Exploratory testing is basically what everyone unfamiliar with the work thinks QA spends all of our time doing. Naturally, it’s not the most sophisticated view, and it’s a topic that’s been basically irrelevant to the past 20 years of Quality Engineering. Good exploratory testers are like rockstar programmers; very powerful most of the time but not as reliable because they spend more of their time innovating rather than maintaining.
To find bugs as soon as possible after they’re inserted into code, you need to find the bugs that cannot be individually predicted. You probably don’t know exactly how the software you test is going to break next. If you’re load or performance testing, you probably don’t have a solid expectation of the results before the first few runs.
So it’s best to know what you’re dealing with, to get the exploratory testing under control and make it as useful and efficient as possible.
Leave a Reply
You must be logged in to post a comment.