Exploratory Session-Based Testing (SBT)
Exploratory Session-Based Testing (SBT) is a structured form of exploratory testing where testing is performed in time-boxed sessions with clear objectives, scope, and reporting, while still allowing tester creativity and learning.
SBT answers: “How can we explore the application systematically without rigid test cases?”
1. Definition
Exploratory Session-Based Testing (SBT) is a structured form of exploratory testing where testing is performed in time-boxed sessions with clear objectives, scope, and reporting, while still allowing tester creativity and learning.
2. Why Session-Based Exploratory Testing Is Needed
- Pure exploratory testing can feel unstructured
- Management needs visibility and accountability
- Testers need freedom with discipline
SBT combines:
- Exploration (learning + testing + design at the same time)
- Structure (sessions, charters, reports)
3. Core Concepts of Session-Based Testing
3.1 Session
- A time-boxed testing period (usually 60–120 minutes)
- Focused on a specific mission
3.2 Charter
- A clear mission or goal for the session
- Defines what to explore, not how to test
3.3 Tester
- Executes the session using skill, intuition, and heuristics
3.4 Session Report
- Documents findings, coverage, issues, and questions
4. Session Charter (Most Important Element)
A Session Charter typically includes:
- Feature / area to explore
- Risks or focus areas
- Constraints (data, environment)
Example Charter:
Explore checkout flow focusing on discount application and error handling.
5. Session Time-Boxing
Typical session length:
- 60–90 minutes (ideal)
- Short enough to stay focused
- Long enough to discover meaningful issues
6. Activities During a Session
During one session, the tester:
- Learns the feature
- Designs tests on the fly
- Executes tests
- Observes behavior
- Notes defects, risks, and questions
All happen simultaneously.
7. Session Report Contents
A session report usually includes:
- Session ID
- Charter
- Time spent
- Test notes
- Defects found
- Risks identified
- Open questions
This provides traceability and visibility.
8. Manual Tester’s Role
- Design effective charters
- Apply domain knowledge and heuristics
- Observe patterns and anomalies
- Document findings clearly
- Share insights during debrief
9. SBT vs Traditional Test Case Execution
| Aspect | Session-Based Testing | Test Case Testing |
|---|---|---|
| Structure | Semi-structured | Fully structured |
| Creativity | High | Low |
| Documentation | Lightweight | Heavy |
| Best for | New, changing areas | Stable features |
10. When to Use Exploratory Session-Based Testing
- Early testing of new features
- Agile sprints with frequent changes
- Complex workflows
- Risk-based testing
- Time-constrained testing
11. Common Defects Found
- Workflow gaps
- Usability issues
- Data handling issues
- Missing validations
- Unexpected system behavior
12. Common Mistakes
- No clear charter
- Sessions too long
- Poor documentation
- Treating SBT as random testing
13. Interview-Ready Answers
Short answer:
Session-based testing is a structured form of exploratory testing using time-boxed sessions with defined charters and reports.
Detailed answer:
Exploratory session-based testing combines tester creativity with discipline by using time-boxed sessions, clear charters, and session reports to provide accountability and effective defect discovery.
14. Key Takeaway
Exploratory Session-Based Testing delivers high defect discovery with structure, making it ideal for Agile, risk-focused, and fast-changing environments.