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. A charter such as explore checkout with expired cards keeps the session focused without scripting it.
No account needed · Scored in under a minute against a senior rubric
What does Session-Based Test Management mean in practice?
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 do interviewers ask about Session-Based Test Management?
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.
What does Session-Based Test Management look like in a real project?
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.
How should you talk about Session-Based Test Management in an interview?
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.
Go Deeper on Session-Based Test Management
Know the term. These are the courses that turn the concept into something you can demonstrate.
Common questions about Session-Based Test Management
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.
Which terms relate to Session-Based Test Management?
Explore related glossary terms to deepen your understanding.
Related Resources
Dive deeper with these related interview prep pages.
Free QA career tools, no account needed
Instant and private, everything runs in your browser. Try them before you sign up.
QA Resume Checker
Instant 0-100 score on automation keywords, impact, and ATS formatting.
QA Cover Letter Generator
A tailored 3-paragraph QA cover letter from your resume and a job post.
QA Application Tracker
Drag-and-drop kanban to track every QA application from Applied to Offer.
QA Take-Home Test Generator
A realistic take-home assignment with a scenario, tasks, and a rubric.
QA LinkedIn Headline Generator
A recruiter-searchable headline, About section, and skills list.
QA STAR Story Builder
Structure a QA behavioral answer with the STAR method and instant checks.
QA Bug Report Generator
Build a clean, reproducible bug report for Markdown, Jira, or plain text.
Boundary Value Analysis Generator
Generate boundary value and equivalence partitioning test cases from a range.
QA Metrics Calculator
Calculate DRE, defect leakage, defect density, and pass rate with interpretation.
QA Test Plan Generator
Build a structured test plan (scope, approach, criteria, risks) in Markdown.
QA Salary Calculator
Estimate QA, SDET, and automation tester pay by level, market, and skills.
QA Offer Evaluator
See total comp, a counter range, and a ready-to-send negotiation message.
Ready to Ace Your QA Interview?
Practice explaining session-based test management and other key concepts with our AI interviewer.
Join 500+ QA engineers already practicing with AssertHired.
A test passes locally but fails in CI about one run in five. Walk me through what you check first, and why.
Scored on the same four dimensions as the real thing: Technical accuracy · Coverage · Clarity · Best practices.
Rather skip ahead? Create a free account