Exploratory testing is an approach to testing software, often compared to “scripted testing,” and characterized by:
- Accentuating the tester’s autonomy, skill, and creativity.
- Recommending the performance of various test related activities performing various test-related activities throughout the development.
- it gives special attention to the mutually supportive nature of the used techniques, and the need for more testing approaches instead of a regular “test plan”.
Agile teams usually shift and redraw the boundaries between “developer” and “tester” as a result of the heavy use by developers of automated unit and functional tests – These activities are not enough to make sure the final product is of quality and Agile teams can find in team members who have well-developed testing skills, some valuable assets.
Also Known As
The term “exploratory testing” has been shared in the testers community, who claim affiliation with a “school of testing thought” known as the “Context-Driven” school, which they differentiate from other schools’ favoring different approaches to testing.
- In 2001 this concept is firstly introduced by Kaner, Bach and Pettichord’s in “lessons learned in software testing”.
- In 2008 Cem Kaner shares his idea of the definition of exploratory testing reflecting the continuing refinement of this approach to testing.
The Agile movement has contributed a lot to the interest from the developer community in the activities of testing, which used to be seen as a skilless job that didn’t require much. However, it has also led to lessened respect for the value of skilled testers, as a result of shifting some test-related responsibilities to the developer role.