Skip to main content
GlossaryTest Design TechniquesSession-Based Testing

Session-Based Testing

Session-based testing structures exploratory testing into time-boxed sessions with a defined charter (a goal or area of focus), producing a session report documenting what was tested, what was found, and what still needs coverage. It brings accountability and repeatability to otherwise unstructured exploration.

A typical session runs 60-90 minutes against a specific charter — "explore the new bulk-edit feature for data integrity issues" — with the tester taking notes throughout on test ideas, bugs found, questions raised, and areas still uncovered, rather than working from a pre-written script.

The session report afterward is what distinguishes this from plain exploratory testing: it makes the coverage and findings visible and reviewable by the rest of the team, turning what could be an untrackable individual activity into something a test lead can actually manage and build on.

Session-Based Testing — Definition, Example & How It's Used | QA Bash Glossary | QA Bash