A big part of examining an app, a website, or another piece of software is learning to ask the right questions. By asking the right questions, you learn more about what is expected and unexpected behaviour. This helps you figure out what the known (and unknown) boundaries of that product are.
Getting into this mindset is important, not just for software testers but for the people working with them as well. Sometimes you need to ask yourself, what isn't being tested? What blind spots do we have? What biases do our testers have?
It's worth it to read all six of the tips, but my favourite are tips 4 & 5:
Asking “Why?” five times is a popular root-cause analysis activity. It’s an iterative question-asking technique used to explore the cause-and-effect relationships underlying a problem.
Here’s an example:
The vehicle will not start. (The problem)
Because you continued asking why, you finally got an answer that gives the root cause.
... Although it’s usually a programming technique, the idea is applicable in software testing as well. Of course, you can explain the problem to your peers to jumpstart your thinking instead, but asking the rubber duck keeps you from interrupting your coworkers—and it sounds more fun.
Besides asking the right kinds of questions, what else is part of the software testing and QA mindset? Share your tips with us.
Going beyond software Customers come to test IO for many different reasons. Sometimes, an internal product or QA team needs a force multiplier for real-world testing – to extend the existing QA team’s processes and activities beyond their internal team. Other times, it’s crisis mode – perhaps QA leadership has left the company, or there is a critical product release upcoming that […]
Here's our guide to which method you should use you to distribute your IOS app to the crowd.
Exploratory testing emphasizes creativity and learning. Test Case testing emphasizes planning and execution. Which one is right for you?
