Exploratory testing is a technique of using knowledge,experience,intuition and skills to test software in a nonlinear investigatory fashion.
“Exploratory testing involves simultaneously learning,planning,running tests and reporting/troubleshooting results.” – Dr.Cem Kaner (2001)
Exploratory testing comes into picture:
When there is no sufficient documentation and you just have the software to test.
When you need to complete your application testing in short period of time.
When you have to test the application in the early stage of SDLC.
EXPLORATORY TESTING is an approach to testing that is very different from scripted testing.As exploratory testing does not follow any fundamental test process like scripted testing.The focus of exploratory testing is more on testing as a “thinking”
Scripted Test Execution is usually a non-thinking activity where testers execute the test steps and compare the actual results with expected results. Such test execution activity can be automated does not require much cognitive skills During Exploratory Testing You need to unlearn everything you know about the software. Think freshly as a guideless client and perform tests on your software, chances are more of discovering bugs during exploratory testing than in formal testing approach based on test cases.
Create a conjecture(mental model).
Design one or more test that would disprove the conjecture.
Execute the tests and observe outcome.
Evaluate outcome against the conjecture.
Repeat the process until the conjecture is proved or disproved.
CHARTERED EXPLORATORY TESTING:
When performing “Chartered exploratory testing” a charter is first created to guide tester within the timebox.
Charter focus the exploratory tester’s effort within the time box.
SESSION BASED TEST MANAGEMENT:
A method for measuring and managing exploratory testing.
Session-Based Test Management as an approach to make those intangibles more tangible. It can be thought of as structured exploratory testing, which may seem like a contradiction-in-terms, but “structure” does not mean the testing is pre-scripted. It implies we have a set of expectations for what kind of work will be done and how it will be reported.As in a recording studio, this work is done in “sessions”. Sessions range from 45 minutes to several hours, but no matter the length, it is time spent testing against a charter for the session.
Testing is complex, but effective use of exploratory techniques can help tame that complexity and contribute to the production of high-quality software.