Internal QA can be expensive and time consuming. Here is how crowdtesting can help.
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.
Internal QA can be expensive and time consuming. Here is how crowdtesting can help.
I asked our CSMs what it takes to get the most from a crowdtest.
