I have gone thro' certain articles about Exploratory Testing, written by James Bach, Cem Kaner and others. But I am still confused over certain terms.
1. Do we need any project related documents for performing exploratory testing? (a) If yes, they could have been converted into test cases or scripts well ahead of the testing schedule know? (b) If no, then how come the tester is going to understand the functionality or the requirements of the AUT?
3. Should Exploratory Testing be done also in projects where Test Case design has been done prior to Testing. If Yes, then it means to say that the tester has not performed a good job while designing know?
Waiting for your valuable suggestions and guidelines.
Re: Exploratory Testing
Do we need any project related documents for performing exploratory testing? (a) If yes, they could have been converted into test cases or scripts well ahead of the testing schedule know?
Yes in my point of view there a project related documents which are usefull in the exploratory testing - for example all of the analysis done in concern of the risk analysis, change impact, test focus areas... However this doesnt mean that the mentioned documents are straightforward converted into test cases and even less into test script. On other side all of the mentioned document may force you to think about the test focus - and this is the fuel for exploratory testing. On other side - the terms "well ahed of the testing shedule" are not in the realm of the exploratory testing. Exploratory testing is best fitted into impossible deadline and tight budgets - this when it comes to full power, not in the medium-paced races( not to say that it is not usefull also in such cases)
(b) If no, then how come the tester is going to understand the functionality or the requirements of the AUT?
There a a myriad of ways to understand the requirements or the functionality - and test cases should be based on the allready understanded functionality. It might lead to misunderstandings if one tries to understand the app using the written test cases..
Senior QA Engineer
Re: Exploratory Testing
The nature of exploratory testing is that it isn't scripted in advance. Documenting what you have learned, or adding test cases, etc during or after is generally thought of as a good practice.
Exploratory testing is generally considered a good way to learn about the app, much better than scripted testing, actually, in many cases.
Exploratory, ad-hoc, "taking a look around", "I wonder what happens if..." whatever you call it, I've never met a tester that doesn't do it at least some. Sometimes it's formal and acknowleged, sometimes it's informal and outside of the plan... either way it happens. The questions really are about whether or not it is encouraged, and what to do when you "find stuff" while you're doing it.
I fully support and agree with Cem and James' articles, but remember where they come from. Exploratory testing is not new or revolutionary. Cem and James just brought it into the public eye and gave it some form and lessons learned (no easy task, but still). My recommendation is, don't overthink it, do what makes sense.