Atlas › 11 Manual Testing Fundamentals › Session Reports☰ Read as one page
Session Reports
4.1OverviewSession reports are the tangible output of exploratory testing. Without them, exploratory testing is invisible work — valuable bugs may be…4.2The Session Report TemplateEvery exploratory session should produce a report. Keep it lightweight — the goal is to capture observations in real time, not write a…4.3Anatomy of Each SectionRestate the original charter. If you deviated during the session (which is acceptable), note the deviation:4.4Note-Taking Strategies During SessionsTaking notes while actively testing is the hardest part of SBTM. Here are practical approaches:4.5Aggregating Session ReportsIndividual session reports become powerful when aggregated across a release cycle.4.6Integrating Exploratory Findings into the Test ProcessExploratory testing does not exist in isolation. Its findings should feed into other testing activities:4.7Why Exploratory Testing Survives AutomationAutomation verifies what you already know should work. Exploration discovers what nobody thought to check. The two are complementary.4.8Practical Exercise1. Choose an application you use daily 2. Write three charters for different features 3. Execute a 30-minute session on the first charter…4.9Key Takeaways- Session reports make exploratory testing visible, accountable, and reproducible - Every report needs: charter, areas covered, bugs found…