Tobias Geyer discusses exploratory ensemble testing, a team-based approach to testing that involves rotating roles and combining it with a charter to guide sessions. This method has helped identify various issues and enhanced test knowledge among developers, promoting awareness of edge cases and out-of-the-box testing scenarios.

Richard Seidl Software Testing

This is the other podcast on Software Testing by Richard Seidl, the episodes are in spoken German but the show notes and site are written in English. Our summaries are generated from AI transcript translations.

• https://www.richard-seidl.com/en/blog/tag/podcast-software-testing
• https://www.richard-seidl.com/en/

Episode Details

• Show Notes: https://www.richard-seidl.com/de/blog/exploratives-ensemble-testing
• Published: 2026-01-20T05:00:00Z
• Duration: 1253
• Author: Richard Seidl - Experte fur Software-Entwicklung und Testautomatisierung

Overview

The podcast covers exploratory ensemble testing, a collaborative testing method where team members take on rotating rolesdriver, navigator, and observerto conduct unscripted testing based on a charter rather than fixed test cases. This approach was initially tested remotely following a workshop and later integrated into development projects. It has demonstrated benefits such as improved team collaboration, the discovery of usability and workflow issues, and increased developer awareness of edge cases. Although early implementation encountered challenges like role confusion and session overruns, the overall results have been positive, with critical bugs identified and a shared understanding of testing practices fostered among team members.

The testing method has since been institutionalized, occurring regularly every four weeks, and continues to be refined for improved effectiveness. The approach emphasizes flexibility and collaboration, allowing teams to adapt to changing project needs while maintaining a focus on identifying potential issues through dynamic, session-based testing. The continued use and refinement of this technique suggest its value in enhancing software quality and team dynamics within development environments.

What If

• What if you simulate exploratory ensemble testing by acting as both driver and navigator in 45-minute sessions every 4 weeks?
  Move: Allocate 45 minutes weekly to test your product using a clear charter, switching between “driver” (exploring features) and “navigator” (guiding based on user workflows) roles.
  Why now: The text highlights that regular sessions (every 4 weeks) maintain novelty and help avoid over-repetition. This rhythm keeps you engaged and ensures testing is not postponed.
  Expected upside: Discover usability issues, edge cases, and workflow errors, similar to how teams found a drag-and-drop bug in the text.

• What if you incorporate internal customer feedback into your testing by role-playing personas once a sprint?
  Move: Create user personas (e.g., “admin” or “end-user”) and act as an “internal customer” during testing, asking questions like, “Would this confuse someone new?”
  Why now: The text mentions the desire to involve internal departments as “customers,” which adds diverse perspectives. This is practical even for solo operators.
  Expected upside: Identify gaps in user experience and align your work with real-world expectations, reducing post-release errors (as seen in Vestass cost-saving example).

• What if you use a 15-minute “role rotation timer” during testing to stay focused and avoid over-running sessions?
  Move: Use a timer to switch between driver (testing) and observer (taking notes) roles every 15 minutes. Record findings in a shared doc for later review.
  Why now: The text notes that ignoring session timers leads to overruns and frustration. This ensures structured testing even as a solo operator.
  Expected upside: Keeps sessions productive and prevents burnout, while capturing actionable insights (like the critical drag-and-drop issue found in the text).

Takeaway

• Schedule Exploratory Testing Sessions Regularly
  Set aside time every four weeks for exploratory testing, using a defined charter to guide your testing without scripted test cases, ensuring it stays aligned with your projects goals and timelines.

• Implement Role Rotation in Solo or Small-Team Sessions
  Even as a solo operator, mentally rotate roles (driver, navigator, observer) during testing to cover different perspectives, simulating ensemble dynamics and improving session depth and engagement.

• Use Charter-Based Testing to Explore User Workflows
  Create testing scenarios based on user workflows (e.g., critical features or pain points) instead of focusing only on unit tests, which helps uncover usability issues and edge cases that scripted tests might miss.

• Involve Stakeholders for Real-World Feedback
  Include internal or external stakeholders (e.g., clients, product managers) in your testing sessions to simulate user behavior, though structure sessions to prevent dominance by non-development participants.

• Adopt Note-Taking Tools That Minimize Interruption
  Use voice-to-text or automated note-taking tools during testing to reduce disruptions, ensuring you capture insights without breaking the flow of exploration, and review notes afterward with stakeholders to refine priorities.