Q33 of 38 · Test design

When do you choose exploratory testing over scripted test cases, and how do you make the output auditable?

Test designMidtest-designexploratory-testingscripted-testingsbtmtest-strategy

Short answer

Short answer: Choose exploratory testing when the risk is poorly understood, the system is new, you are investigating a bug's blast radius, or when scripted tests would require more design time than the feature is worth. Make it auditable through session-based test management: a charter, time-box, and a written session report.

Detail

Scripted test cases are appropriate when: behaviour is well-specified, regression coverage is the goal, the test will run repeatedly, or compliance requires documented test execution records.

Exploratory testing is appropriate when: requirements are incomplete or ambiguous, you need to learn the system before you can design tests, a production incident revealed unexpected behaviour and you are mapping the risk, or the feature is too dynamic for scripted cases to stay current.

To make exploratory testing auditable, use session-based test management (SBTM): write a charter before the session, time-box to 60–90 minutes, and produce a session report afterwards with findings, bugs raised, coverage notes, and questions. This satisfies audit requirements without the overhead of maintaining test case documents for fast-moving areas.

// WHAT INTERVIEWERS LOOK FOR

Knowing that exploratory and scripted testing are complementary, not competing. Clear criteria for choosing each. SBTM as the mechanism for making exploratory testing visible and auditable.