Session Sheets and Test Logs in Session-Based Testing

Session Sheets and Test Logs in Session-Based Testing (ISTQB CTAL-TA): A Complete Guide

Introduction
Session-Based Test Management (SBTM) is a way of managing exploratory testing. It was developed by Jonathan and James Bach. Exploratory testing is often criticised as unstructured, unmeasurable and hard to audit. SBTM answers that criticism by organising the work into time-boxed sessions and documenting each one in a session sheet, which contains a test log.

The ISTQB Certified Tester Advanced Level Test Analyst (CTAL-TA) syllabus covers session-based testing under Experience-Based Testing. You are expected to understand how exploratory testing is planned, executed, recorded and reported, and session sheets and test logs are at the centre of all four.

Why Session Sheets and Test Logs Are Important
1. Accountability and traceability. Exploratory testing designs tests during execution, so there are no pre-written scripts. The session sheet becomes the record of what was tested, how, and what was found. Without it, managers and stakeholders cannot see what testing actually happened.

2. Measurability. Session sheets capture metrics such as session duration and the share of time spent on test design and execution, bug investigation and reporting, and session setup. Managers use these figures to judge productivity, find obstacles and estimate remaining effort.

3. Coverage assessment. Each session is tied to a charter and records the areas covered, so test leads can combine sheets to see which areas have been explored and which have not. This supports risk-based decisions.

4. Reproducibility of defects. The test log records the steps, data and observations made during the session. Testers can use it to reproduce and report defects accurately.

5. Debriefing and learning. The sheet is the main input to the debriefing with the test manager or lead. In the debrief, results are reviewed, the next charters are decided, and coaching takes place.

6. Compliance and auditability. In regulated or contract-driven environments, session sheets provide evidence that exploratory testing was carried out in a controlled and documented way.

What Is a Session?
A session is an uninterrupted, time-boxed period of focused testing, typically 60 to 120 minutes. Sessions are often classed as short (about 60 min), normal (about 90 min) or long (about 120 min). Each session:
- is guided by a test charter stating the mission (what to test, what to look for, sometimes how)
- is carried out by one tester or a pair
- produces a session sheet (also called a session report)
- ends with a debriefing

What Is a Session Sheet?
A session sheet is the standard document that records one session. It usually contains:
Charter: the mission or objective of the session.
Tester name(s): who performed the session.
Date and start time: when the session happened.
Duration: how long the session lasted, often given as a session size.
Task breakdown (time allocation): percentages of time spent on:
- Test design and execution: the actual testing activity
- Bug investigation and reporting: time spent analysing and documenting defects
- Session setup: time spent configuring environments, preparing data, and so on
Charter vs. opportunity: the ratio of time spent on the charter compared with time spent on valuable tangents (opportunity testing).
Data files: test data, screenshots, logs or other artefacts used or produced.
Test notes / test log: a narrative or bulleted record of what was done and observed.
Defects (bugs): defects found, often with IDs.
Issues: questions, obstacles, concerns, or problems that are not defects. Examples are an unavailable environment, unclear requirements or missing tools.
Areas covered: product areas, features, configurations or strategies covered.

What Is a Test Log in Session-Based Testing?
The test log (or test notes) is the part of the session sheet where the tester records the testing activities chronologically or by theme. Unlike a scripted test log that records pass/fail against predefined cases, this log captures:
- the ideas and test conditions explored
- the inputs used and actions taken
- the observed behaviour and outcomes
- the reasoning behind choices (why a path was pursued)
- the heuristics, oracles or techniques applied
- observations worth following up, including potential risks

The CTAL-TA syllabus says that in exploratory testing, test design and execution happen at the same time. The log must therefore be detailed enough for others to understand what was tested, assess coverage and reproduce defects. It must also stay lightweight, so the tester does not lose focus on testing.

How Session-Based Testing Works: The Lifecycle
Step 1: Create the charter. The test analyst or manager writes a charter based on risks, requirements, previous findings or test basis analysis. Example: Explore the checkout process with invalid payment data to discover error-handling weaknesses.

Step 2: Prepare the session. The tester sets up the environment and data, and records setup time on the sheet.

Step 3: Execute the time-boxed session. The tester explores the system in line with the charter, applying techniques such as boundary probing, tours, error guessing or attack-based testing. While testing, they keep the test log, noting actions, observations, defects and issues.

Step 4: Complete the session sheet. At the end, the tester finalises the sheet with the time breakdown, defects, issues, areas covered and charter vs. opportunity ratio.

Step 5: Debrief. The tester and the test lead or manager review the sheet together. A common checklist is PROOF:
- Past: what happened during the session?
- Results: what was achieved?
- Obstacles: what got in the way?
- Outlook: what still needs to be done?
- Feelings: how does the tester feel about the session?

Step 6: Aggregate and report. Metrics from many session sheets are combined to report progress, coverage and quality status, and to plan further sessions.

Typical Metrics Derived from Session Sheets
- Number of sessions completed
- Number of defects found per session
- Percentage of time on testing vs. bug investigation vs. setup
- Coverage of product areas
- Charter vs. opportunity time
- Number of issues raised (often a sign of process or environment problems)

For example, a high share of setup time suggests environment problems. A high share of bug investigation time suggests a buggy area or poor testability.

Relationship to the Test Analyst Role
Per CTAL-TA, the Test Analyst:
- designs charters based on risks and the test basis
- performs sessions using experience, domain knowledge and techniques
- documents results in session sheets and test logs
- participates in debriefs
- supports the Test Manager by providing the data needed to monitor and control testing

Exam Tips: Answering Questions on Session Sheets and Test Logs in Session-Based Testing
Tip 1: Know the components of a session sheet. Questions often list items and ask which ones belong on a session sheet. Correct items include the charter, tester, date/time, duration, time breakdown, test notes, defects, issues, data files and areas covered. Be wary of options such as detailed pre-written test procedures or expected results for every step. Those belong to scripted testing.

Tip 2: Distinguish defects from issues. A defect is a problem in the test object. An issue is anything that blocks or concerns the testing, such as a missing environment, unclear requirements or a tool failure. Exam questions may test whether you can classify these correctly.

Tip 3: Remember the three time categories. These are test design and execution, bug investigation and reporting, and session setup. If a question asks what a high percentage of setup time indicates, the answer is usually an environment or tooling problem, not a low-quality product.

Tip 4: Understand the purpose of the test log. In session-based testing, the log records what was actually done and observed, because tests are designed during execution. Its purposes are traceability, reproducibility, coverage assessment and debrief input. It does not record pass/fail against predefined test cases.

Tip 5: Link sheets to debriefing. Many questions ask what happens after a session. The answer is a debrief using the session sheet, possibly following PROOF. If an option says the session sheet is archived without review, it is likely wrong.

Tip 6: Charter vs. opportunity. Opportunity testing (following valuable tangents outside the charter) is acceptable and encouraged when it is justified. It must be recorded. A question may ask how a tester should handle an interesting but off-charter finding. The best answer is to note it, pursue it briefly if valuable, and record the time as opportunity, or else propose a new charter.

Tip 7: Scenario-based questions. At Advanced Level, expect scenarios. For example: A manager wants evidence that exploratory testing covered the high-risk areas. Which artefact provides this? Answer: the session sheets, specifically the charters and areas covered sections, aggregated across sessions.

Tip 8: Watch for absolute words. Options with always, never or must contain every step are usually wrong. Session documentation aims for a balance: enough to be useful, without over-documenting.

Tip 9: Time-boxing is key. Sessions are uninterrupted and time-boxed. If a question describes testing that is constantly interrupted with no defined duration, it does not follow SBTM principles.

Tip 10: Connect to monitoring and control. Session sheet metrics feed test progress reporting. If asked how exploratory testing can be managed and measured, mention session sheets, metrics and debriefs.

Tip 11: Eliminate scripted-testing distractors. Wrong answers often borrow from scripted testing: test case specifications, traceability matrices with expected results, or detailed step-by-step procedures. Session-based testing uses charters and logs instead.

Tip 12: Read the stem carefully. Identify whether the question asks about the charter (the plan), the session sheet (the record), the test log (detailed notes within the record) or the debrief (the review). Confusing these four is the most common cause of lost marks.

Sample Question Walkthrough
Question: During a 90-minute session, a tester spent 50% of the time configuring test data and resolving environment problems. Which is the BEST interpretation during the debrief?
a) The product has many defects
b) The tester is inexperienced
c) There are obstacles in the test environment that should be addressed
d) The charter was too broad
Answer: c). The time was recorded as session setup, which points to environment or data obstacles. Those should be raised as issues and resolved. They fall under the Obstacles part of PROOF.

Summary
Session sheets and test logs make exploratory testing visible, measurable, reviewable and manageable while keeping its flexibility. For the CTAL-TA exam, make sure you know:
- the elements of a session sheet
- the purpose and content of the test log
- the time categories
- the difference between defects and issues
- the charter vs. opportunity concept
- the role of debriefing
- how session metrics support test monitoring and control

With these points mastered, you can confidently handle both factual and scenario-based questions on the topic.