20 / 71 · 11 Manual Testing Fundamentals · SBTM Methodology← prev⊞ allnext →☰ Read as one page
3.4Sessions
A session is a focused, uninterrupted block of testing, typically 60-90 minutes. The time constraint is essential: it prevents exploration from becoming aimless wandering.
Session Structure
| Phase | Duration | Activity |
|---|---|---|
| Setup | 5-10 min | Review charter, prepare environment, load test data |
| Exploration | 40-70 min | Active testing, note-taking, bug filing |
| Wrap-up | 5-10 min | Organize notes, draft bug reports, prepare for debrief |
Rules During a Session
- No interruptions. Treat it like a focused work block. Close Slack, mute notifications.
- Stay on charter. If you discover something outside your charter, note it as a new charter for a future session.
- Take notes continuously. If you stop taking notes, you stop doing exploratory testing and start doing random testing.
- Time-box strictly. When time is up, stop. You can always schedule another session.
Session Metrics
Track these metrics across sessions to understand your testing effort:
| Metric | Definition |
|---|---|
| Session count | Total sessions conducted for this release |
| Bug count | Issues found per session |
| Charter coverage | Percentage of planned charters completed |
| Test vs investigation ratio | Time spent testing vs investigating bugs |
| Session notes density | Volume of observations per session (sparse notes = unfocused session) |