Library › Book 11 › Session Reports and Note-Taking
Session Reports and Note-Taking
4.1🔒The Session Report Template
4.2🔒Note-Taking StrategiesTaking notes while actively testing is the hardest part of SBTM.
4.3🔒Aggregating ReportsTrack coverage across sessions:
4.4🔒From Exploration to Other ActivitiesThe virtuous cycle:
4.5🔒Key Takeaways — Chapter 4- Session reports make exploratory testing visible and accountable - Every report needs: charter, areas covered, bugs, questions…
4.6🔒Exercises — Chapter 4Beginner: Read the example session report above and identify: How many bugs were found? What severity were they? What would the tester do…
4.7🔒Q&AResume phrasing- Produced structured session reports for every exploratory testing cycle, providing stakeholders with evidence-based coverage metrics and…
4.8🔒Q&ACover letter framingI believe that undocumented testing is invisible testing. My session reports transform exploratory work into actionable intelligence: what…
4.9🔒Q&AInterview framing"I approach session documentation as the bridge between doing the testing and proving the testing happened. I take notes in real time using…
4.10🔒Q&AWhat not to say- "I don't write reports for exploratory testing because it's informal" — makes exploration invisible and unaccountable - "I just file bugs…
4.11🔒Q&AQuestion 1Prompt: You completed five exploratory sessions over two days. Your test lead asks: "How do I know what's been tested and what hasn't?" How…
4.12🔒Q&AQuestion 2Prompt: A tester on your team writes session reports that just say "Tested the search feature. Found 2 bugs." How do you coach them to…
4.13🔒Q&AQuestion 3Prompt: You ran an exploratory session and found zero bugs. Does that mean the session was wasted? How do you present this to stakeholders?…
4.14🔒Q&AQuestion 4Prompt: Your session notes reveal you spent 40 of 60 minutes on an area outside your charter because you found something interesting. How…