- Is there any standard or pattern of doing Exploratory Testing?
- Do we still need to write test cases or not?
- Is there any flow to follow with this kind of testing?
- How Exploratory Testing related with ‘Recon Testing’?
No, there is not a defined industry standard pattern.
There is not a set definition for exploratory testing. I would read the Exploratory Testing 3.0 blog of James Bach though, as it explains the continuum going from totally free-style-exploring to exploratory-scripted.
The exploratory-scripted continuum. This is a sliding bar on which testing ranges from completely exploratory to completely scripted. All testing work falls somewhere on this scale. Having recognized this, we stopped speaking of exploratory testing as a technique, but rather as an approach that applies to techniques (or as Cem likes to say, a “style” of testing).
Your second question:
Do we still need to write test cases or not?
Yes ofcourse, but maybe not as a part of formal documentation.
Often I throw away my test-cases after an exploratory testing session. If we find defects we write a new automated test for it anyways.
We mostly use exploratory testing to find gaps in our test automation, as I describe in the Lookout part in my Test-EiffelTower blog, but also for a usability sanity check of-course. It clearly depends on the needs and the charters we define. Also what we test depends on where we are in the project.
Your third question:
Is there any flow to follow with this kind of testing?
When I teach exploratory testing methods I tend to let newbies start with the following format:
- Timebox: Set a timebox (90min +-45min)
- Understand the product/feature: Create a mindmap and charters. (update them next loop)
- Design tests: Pick some heuristics to validate areas of the map or charters
- Execute tests: Execute a few tests. Log your steps and results.
- Analyse: Analyse your results. Use root-cause-analyses to go deeper. Defects-cluster
- Loop: Is your timebox finished? Yes: Goto step 7. No: goto step 2.
- Stop: Stop testing and share your results with the team. Decide what the next actions will be. (Could also be another exploratory testing cycle.)
After practising this a couple of times feel free to go more scripted or more free-style. Depending on industry, project or personal-style.