Exploratory testing is fast catching up with the testing community in the context of agile. Exploratory testing is a form of ad hoc testing. But ad hoc testing is considered to be more unstructured and does not get a thumbs up with the project teams.
Moin Syed, Principal Consultant – Advisory & Transformation Services at Cigniti Inc., explains in this blog how exploratory testing fits nicely in the context of agile testing. The objective behind the exploratory testing should not just be to perform it but to find better ways to execute and to think to what level it should be performed.
We can define exploratory testing as a progressive approach where the testers have to perform multiple things simultaneously; understand the application functionality, develop test design and execute tests.
The benefit of exploratory testing is that it is not just driven by the documented steps but evolves with the testers’ imagination and insight into the application.
Now to fit exploratory testing in an agile context, it cannot be ad hoc. It needs to be time boxed to align with agile structure. Boundaries of the exploratory testing should be defined within the sprint timebox.
The below categories will help create a framework of sort to define and conduct exploratory testing:
- Landscape: what the product is
- Functionality: what the product does
- Data Flow: what it processes
- Platform: what it runs on
- Operations: Who will use
Exploratory testing will make agile testing more result driven. It is an efficient and effective method to test software. It gives the much-needed results immediately and finds the critical defects faster. Slowly it is becoming an industry standard for manual testing.