Getting The Most Out of Team Exploratory Testing Sessions
summary
Claim: team exploratory testing shifts ownership of quality and reduces tester bottlenecks. Concrete setup: 1 hour: 10/35/15 split with a shared dashboard with scenario boxes, links to user story maps and designs, and priority tags. Tools and context: remote execution via Zoom or Teams, testers facilitate while all roles test. Numbers and results: practiced at Glox with seven devs + one tester, recommends about eight people, produces prioritized findings, raises developer confidence, and surfaces process fixes like adopting three‑amigo sessions.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:47First exploratory session
- 3:52What is team exploratory testing
- 5:40Session dashboard template
- 8:11Running the session
- 10:46Lessons learned
- 12:09Long-term benefits
- 14:43Types of exploratory sessions
- 17:17Key takeaways
- 18:00Q&A
related talks
36mWhole team quality: In the same boat or up the creek?
01h 01mIntersection of Automation and Exploratory Testing
25mHow to Transform Dev and Test Silos into a Team
43mTeaching Testing to Non-Testers
01h 29mDriving Engagement with User Stories
08m“Testers! Aim to Enable”
37mHow to Run 100 User Tests in Two Days
01h 14mVisualizing Testability