Exploratory Testing Why, When and How!

There was a quite an interesting discussion going on at linkedIn regarding Exploratory testing, so I thought of writing this mini blog, and share my views, why I don't consider exploratory testing a valid QA activity in today’s context.

The very first reason behind my thoughts is its timing, “When” you do exploration? Since it is practically possible only in a waterfall SDLC model, when your application is ready. You practically can’t explore things until you have them. In an agile or an iterative development model, it is practically not possible.

Another good reason for the argument is based on “How” you do exploration, well, it is practically possible on a UI based application, not sure how effectively you can explore API’s randomly.

Well, there's a difference between an ad-hoc or random testing Vs Exploratory testing, and to support my argument, we need to ask the question “Why”, we do exploration, well, there are many reasons for it. 

• To verify if users are able to understand this product, without using a manual. 
• Are they able to navigate to the features logically.
• Are they comfortable using the product, including look and feel, font and colours.
• This also includes high level response time, performance, slowness testing etc.

Conclusion:

Exploratory testing has more value at a finished product and therefore it must be done by end users.  Some people interchangeably use the term PoC (proof of concept) for exploration at times.   Exploratory testing could be a very helpful technique while selecting an OTC (over the counter) product for your needs out of multiple choices.

Therefore we can not deny the fact behind its importance, but we need to understand when it makes sense, why it matters.