What is Session-Based Test Management?

Session-based test management (SBTM) is a structured approach to exploratory testing in which testing is organized into time-boxed, chartered sessions with defined goals, recorded notes, and a debrief, making otherwise unstructured exploration measurable, accountable, and reportable.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

IN DEPTH

In depth.

Exploratory testing is powerful but can seem unmanageable to stakeholders who want visibility and metrics. SBTM (introduced by Jonathan and James Bach) adds lightweight structure without scripting every step. Testing happens in focused sessions, typically 60 to 120 minutes, each guided by a charter, a short mission stating what to explore (for example, "explore the checkout flow with invalid payment data"). The tester records notes, bugs, and questions during the session and reports time spent on testing versus setup versus investigating issues.

A debrief (often using the "PROOF" agenda: Past, Results, Obstacles, Outlook, Feelings) follows, where the tester and lead discuss findings, coverage, and what to charter next. This produces session sheets that give managers real metrics, sessions completed, coverage areas, bugs found, while preserving the freedom and adaptiveness that make exploratory testing effective.

SBTM is the answer to "how do you make exploratory testing accountable and trackable?" It keeps the creativity of exploration while adding the planning, measurement, and reporting that scripted testing normally provides.

WHY IT MATTERS

Why interviewers ask about this.

SBTM comes up when interviewers probe how you manage or report exploratory testing. Describing charters, time-boxed sessions, and debriefs shows you can get the bug-finding power of exploration while still giving stakeholders the structure and metrics they need, a senior, pragmatic perspective.

EXAMPLE

Example scenario.

A QA lead charters four 90-minute sessions across a new feature, each with a focused mission. Testers explore freely, record session sheets, and debrief. The result: a measurable view, sessions done, areas covered, twelve bugs found, plus charters for the next round, all without writing hundreds of scripted steps.

TIP

Interview tip.

Define session-based testing as structuring exploratory testing into time-boxed, chartered sessions with notes and a debrief. Emphasize that it makes exploration accountable and measurable (session sheets, coverage, bugs) while keeping the adaptiveness of exploratory testing, the best of both worlds.

FAQ

Frequently asked questions.

How does session-based testing make exploratory testing measurable?

By organizing it into time-boxed sessions, each with a charter (mission), recorded session notes, and a metric breakdown (time on testing vs setup vs bug investigation), followed by a debrief. The resulting session sheets give managers coverage, counts, and findings without scripting every step.

What is a test charter in SBTM?

A charter is a short mission statement that sets the goal and scope of a session, for example, "explore the password reset flow focusing on security and error handling." It gives direction while leaving the tester free to investigate adaptively within that focus.