Exploratory Testing: Principles, Differences from Scripted Testing, and Session‑Based Test Management

Traditional scripted testing (ST) relies on detailed test case documents and a two‑stage process that struggles to keep up with fast‑paced agile development, leading to bottlenecks such as insufficient testing time and heavy maintenance of test artifacts.

To address these issues, agile testing expert Lisa Crispin proposes the test pyramid, originally composed of unit tests, API tests, and GUI automation, with exploratory testing (ET) added at the top as a complementary practice.

Exploratory testing is defined as a method that emphasizes tester autonomy and responsibility, integrating learning, test design, and execution in parallel throughout a project, rather than being a new technique but a new testing style.

The article highlights three key points: ET is a testing style, not a new technique; it aligns with agile values by stressing individual initiative; and it merges learning, design, and execution into a single, iterative loop that provides rapid feedback.

ET also shares agile traits such as minimal documentation and time‑boxed sessions, exemplified by Session‑Based Test Management (SBTM), which structures testing into fixed‑duration sessions with a charter, time box, reviewable results, and debriefing.

A comparison table shows when to prioritize ET versus scripted testing based on requirement clarity and time constraints, suggesting a hybrid approach in most scenarios.

The article concludes that ET’s agile characteristics make it an excellent partner for agile projects, but it is not a universal cure; success depends on testers understanding and practicing ET responsibly.