Software Testing

Intermediate path · lesson 8 of 19

IntermediateTest design5 min readPublished November 12, 2026

Session-based test management

Exploratory testing finds great bugs, but managers ask: what did you cover, and how much is left? Session-based test management answers that with charters, time-boxed sessions, session sheets and short debriefs.

On this page

Key takeaways

  • Session-based test management (SBTM) organises exploratory testing into time-boxed sessions, each with a charter, a session sheet and a debrief.
  • It keeps the freedom of exploration and adds accountability: what was covered, what was found and how much time went into testing itself.
  • The data from many sessions gives managers real progress reports without turning exploration into scripts.

Where this picks up

You've seen the basics of exploratory testing: charters, time boxes, notes. That works well for one tester. But with a team exploring for weeks, questions come up:

  • Which areas have been explored, and how deeply?
  • How much time is spent actually testing, and how much is lost to setup and blockers?
  • When are we done?

SBTM answers those. Jonathan Bach described the method, developed with his brother James Bach, in an article in Software Testing & Quality Engineering magazine in 2000.

The four parts

1. Charters

A charter is the mission of a session. Good charters are specific enough to focus and open enough to explore:

Too vagueGoodToo narrow
Test the appExplore discount codes with expired, reused and stacked codes to discover pricing errorsCheck that code SPRING10 gives 10% off

Keep a charter backlog: a list of planned charters, prioritised by risk. New charters are added as sessions discover new areas.

2. Time-boxed sessions

A session is an uninterrupted block of testing on one charter, typically 60 to 120 minutes. No email, no meetings.

Uninterrupted matters. A two-hour session broken by five interruptions is five short, shallow sessions.

3. The session sheet

At the end, the tester fills in a short report:

FieldExample
CharterExplore discount codes with expired, reused and stacked codes…
Tester, date, durationAna, 12 Nov, 90 min
Time breakdownTesting 60% · Bug investigation and reporting 30% · Setup 10%
On charter vs opportunity80% on charter · 20% following something interesting nearby
Test notesWhat was tried, with which data, what was seen
BugsBUG-412: two codes stack when applied in a second tab
IssuesNo test account with an expired loyalty card; couldn't test that path

The time breakdown is powerful. If testers spend half their sessions on setup, the problem isn't testing, it's the environment.

4. The debrief

After each session, or once a day, the tester and a lead spend 10–15 minutes going through it:

  • What did you cover, and what did you find?
  • What got in the way?
  • What's still worth exploring? Does that need a new charter?
  • How confident are you about this area now?

The debrief is where coaching happens, and where the lead learns things a report wouldn't show.

Reporting from sessions

With session sheets in place, you can report progress like this:

AreaSessions doneBugsConfidenceNext
Checkout64 (1 critical, fixed)High1 regression session after fixes
Discounts33Medium2 charters left: stacking, currencies
Account settings10Low (shallow)2 charters planned

That's a progress report based on what was explored, not on how many scripted tests have run.

Real-world exampleWhere did the testing time go?

A team of four testers explored a new mobile banking release for two weeks. The lead introduced session sheets in week one.

After 30 sessions, the time breakdown showed that only 45% of session time was actual testing. Over a third went to setup: test accounts expired every day, and each tester rebuilt their data by hand.

The lead used the numbers to justify a script that created fresh test accounts each morning. In week two, testing time rose to about 70% of each session, and the team covered the remaining charters on schedule.

Lesson: without session data, the lost time would have looked like "testing is slow". With it, the real cause was visible and fixable.

Making it work

  1. Start with a charter backlog for the release, ordered by risk.
  2. Protect session time. Agree as a team that sessions aren't interrupted.
  3. Keep sheets short. A template that takes 5 minutes is filled in. One that takes 20 isn't.
  4. Debrief every day, even briefly. Unreviewed notes lose their value fast.
  5. Review the numbers weekly: coverage by area, time breakdown, new charters.

Do

Write charters around risks and information you need: "to discover how payment errors are handled".

Don't

Turn charters into step-by-step scripts. Then it's scripted testing with extra paperwork, and you lose what exploration is good at.

Check yourself

Session sheets show testers spend 40% of session time investigating and reporting bugs in one area. What might that tell you?

Show answer

That area is unstable: it produces many bugs, or bugs that are hard to reproduce. It may not be ready for deep testing. Talk to the developers: maybe it needs fixes or developer testing before more exploratory sessions, so testers spend their time finding new problems instead of documenting known ones.