Exploratory Testing

In-attentional bias is one of the most common biases when it comes to testing. Testers
seem to find only what they are looking for and tend to miss the obvious unexpected. In most of
the cases testers try to finish all the test cases and do not take a holistic approach (Owen). One
of the most powerful testing technique to avoid in-attentional bias is exploratory testing.
Exploratory testing involves simultaneous learning, test design, test execution and analysis
(Bach) . Unlike scripted test, the tester does not start with a set of pre-defined test cases, rather
the tester actively controls the design of the tests and uses information gained while testing to
design new and better tests (Bach). So, this approach emphasizes on testers autonomy, skill,
and creativity and like other agile practices, it focuses on people rather than processes.
Session based time management is one of the most widely followed approach for
exploratory testing. This approach involves following steps:

Charter creation The tester identifies a specific testing objective, like testing a

particular functionality, testing a particular workflow or testing a particular scenario

Timebox In exploratory testing, the tester does not have a fixed set of tests to
complete. So, in such situation, it is easy to lose focus. To avoid this situation, the

whole activity should to be time boxed

Explore and learn The tester starts with exploring the application and then designs
tests based on his learning. Then he executes the tests and documents his findings.

Based on his findings he then designs the new set of tests

Debrief It is important to communicate all the findings to the whole team.

Based on degree of structure and usage of already existing documents, there are
various types of exploratory testing namely Freestyle (ad-hoc, no rules), Scenario (create
scenarios and test), Strategy (use known bug finding techniques) and Feedback (use history to
guide testing). Depending upon the project situation and the skillsets of the tester one of these
different styles of exploratory testing can be employed. In exploratory testing, it is very important
to realize that goal of exploratory testing is not just to find bugs, but to understand the
application and force the system to exhibit its capabilities.

References
Bach, J. (n.d.). What is Exploratory Testing? Retrieved from Satisfice Inc.:
http://www.satisfice.com/articles/what_is_et.shtml
Owen, G. (n.d.). Software testing techniques: Overcoming biases. Retrieved from TechTarget:
http://searchsoftwarequality.techtarget.com/tip/Software-testing-techniques-Overcomingbiases

Individual Paper & Presentation

OPIM 5507: Agile Project Management