Exploratory Testing | Types , Features and drawbacks
Exploratory testing is a hands-on approach in which testers are involved in minimum planning and maximum test execution.
The tester is constantly making decisions about what to test next and where to spend the (limited) time.
- Involves concurrent test design, execution, logging and learning how the system behaves by the tester.
- Tester builds a “mental model” of the system while they test it
- Exploratory testing technique is usually used when:
- when there are few or inadequate specifications
- time pressure
- complementing more formal testing
- Less preparation time.
- In less time important bugs are found quickly
Benefits/Advantages for Exploratory testing:
- It takes less preparation.
- Critical defects are found very quickly.
- The testers can use a reasoning based approach on the results of previous results
Some drawbacks of Exploratory testing:
- Tests cannot be reviewed.
- It is difficult to keep track of what tests have been tested.
- It is unlikely to be performed in exactly the same manner and to repeat specific details of the earlier tests.
Types of exploratory testing :
Freestyle exploratory testing
- Adhoc exploration of an application’s features
- No rules, not necessary to account for coverage, past tests, etc.
- Good for familiarizing yourself with an application to prepare for more sophisticated methods like quick smoke tests, sometimes finds bugs
- An extension of traditional scenario testing
- Start with: user stories ,E2E scenarios ,test scenarios and then widens the scope
Strategy based exploratory testing
- Freestyle testing combined with known bug finding techniques
- documented strategies like boundary values
- intuitive instinct from experience or familiarity with the application
- Focus is on learning tips and tricks and recognizing when to apply them
- Test history is built up that acts as feedback to guide future exploration
- Includes- Test history , Coverage ,Churn etc.
- Tools are often an integral part of this type of testing as they ‘remember’ history for us
It is an approach not a technique Also known as Session-Based Test Management (SBTM).