COAST TALKS: Øyvind Stenhaug, QA engineer
By now, you’ve probably already visited our Bug report wizard and talked to us on Facebook and Twitter. We want you to enjoy Coast on your iPad, so remember that you can poke us when you have questions.
Speaking of which, we’re introducing you to Øyvind Stenhaug, our team’s Quality Assurance engineer. When you report something, he’s the one who makes sure it gets fixed.
Øyvind’s handling the nitty-gritty of testing Coast - writing tests, reviewing tests, improving testing tools, monitoring that tests are being run regularly, and making sure that problems are reported and assigned to the appropriate people.
That’s one heck of a job. And Øyvind explains how he does it.
How do you check bugs?
When examining reports from the Bug report wizard or other team members and Opera employees, I check if I can reproduce it. The Bug report wizard, for example, has a “What did you do, step by step” section. This is very important. Reproducing an action means I go through the same steps a user reports to us. If it’s something that wasn’t a problem in earlier versions, I might also check which change it was that introduced the bug. Based on this and/or general examination, I might be able to provide more details about how it needs to be fixed, and to find out which people would be best equipped to do it.
How about manual testing?
I also do that. I try to find things that go wrong. Often this can be focused on the various things that have been changed most recently. If a new feature has been written, I test that to see if it’s unfinished or interferes with existing functionality in bad ways. When something has been fixed (especially if it looks like a complicated or risky fix), I try to check if there are remaining unfixed cases or if the fix has broken something.
What skills are needed when writing tests?
Looks like it takes a lot of time.
Depends. Because we also have the possibility to test some things automatically, with a minimal amount of manual work needed. This is good, because it’s faster and can even be done overnight, so we don’t have to choose which things we have time to test and how often. These tests are written in the Python programming language.
Does it also mean that new tests have to be written or that previous tests have to be changed every time a new feature is added to Coast?
To be more efficient and cover more ground, it’s good to do as much as possible in an automated way. Improvements that might be needed are adding more tools or expanding existing ones to do things we couldn’t before (related to new or existing features), making the ones we have work more reliably, or making them easier to use.
Here’s Øyvind at work while Alex turns up the volume of the office speakers for some music. This was from Øyvind’s Coast-blog debut (and might be his only appearance here). Don’t disturb him. He’s checking your bug report now.
Download Coast by Opera