Skip to content

QA Forum 2025-1-20

QA Forum - January 20, 2025

Topic: Ensemble Exploratory Testing (EET)

Ensemble Exploratory Testing (EET) is a collaborative testing approach where a diverse group of team members work together on a single computer. Roles are rotated frequently, enabling participants to explore, test, and provide rapid feedback on new features or systems.

Key Takeaways from the Session

Introduction to EET

He Li introduced the concept of Ensemble Exploratory Testing to the backend team, highlighting its potential to address current challenges in exploratory testing. The session sparked a passionate discussion about its implementation, with the team eager to explore its benefits.
Here is the introduction slides

Key Insights from the Discussion

1. Role of the Ensemble
  • Shakib cared about the ensemble role
  • Ensemble role should focus on observing and thinking rather than directing the driver.
  • Each team member should be prepared for their turn as a navigator.
2. Test Charters
  • The team raised questions about preparing test charters and whether they might restrict creativity.
    • He Li presented examples of test charters used in previous projects, such as Lithic.
    • He Li suggested simplifying the approach by listing features and preparing resources specific to testing, rather than creating rigid charters.
3. Involving Frontend Developers
  • Ling asked how frontend developers could participate, given that backend and frontend teams typically agree on contracts beforehand.
    • Ensemble exploratory testing focuses on workflows rather than detailed models.
    • Early feedback from the frontend and product teams was encouraged.
    • Cross-team ensembles were suggested, with developers providing:
      • Clear explanations of features
      • Postman collections
      • Test users for testing purposes.
4. Time Constraints
  • Gertian expressed concerns about time constraints.
    • He Li clarified that detailed scenarios are not created; instead, only a feature list is provided.
    • Sessions can be tailored to fit different timeframes, involving only the relevant people.
    • Exploratory testing aids in testing workflows and creating regression tests later.
5. Sequence of Testing
  • Martin asked whether exploratory testing should precede regression testing.
    • Yes, exploratory testing should be conducted first to test workflows and identify which tests could be included in regression.
    • The recommended sequence is as follows:
      1. Set acceptance criteria
      2. Conduct ad-hoc testing
      3. Perform unit/integration testing
      4. Execute exploratory testing
      5. Develop end-to-end regression tests
      6. Perform smoke tests
6. Early Feedback
  • The team also discussed how EET facilitates early feedback.
    • By conducting tests as soon as API workflows are ready, cross-team collaboration allows for immediate feedback and knowledge sharing.

Other Team Reactions

  • Lars: Expressed strong interest and suggested applying EET to the PhonePlan project.
  • Andy: Highlighted that EET could significantly improve cross-team collaboration.

Conclusion

He Li concluded the session by offering to assist the team in initiating Ensemble Exploratory Testing.