Pair Testing and Three Amigos Sessions
Pair testing and Three Amigos are structured collaboration techniques that combine multiple perspectives to produce better quality outcomes than any individual working alone. Both are practical tools any QA engineer can introduce to their team immediately, with no tooling required.
Pair Testing - Two Minds, Higher Quality
Pair testing involves two people collaborating on the same testing session simultaneously - one typically drives (operates the application) while the other observes and guides (suggests test scenarios, watches for unexpected behavior). Pairs work because: the observer catches things the driver misses, two testers generate more creative test scenarios through conversation, complex defects are easier to investigate with two perspectives, and junior QA engineers learn rapidly by pairing with senior engineers. Pair testing is particularly valuable for: exploratory testing of complex features, investigating intermittent defects that are hard to reproduce, testing high-risk areas with critical business impact, and onboarding new QA engineers to a product area. How to suggest it to your team: 'I'd like to try pair testing on the payment flow this sprint - 2 hours together on our most complex feature. I think we'll find more interesting defects than I would alone.'
Technical diagram.
Three Amigos - Collaborative Requirement Refinement
- Who: Product Owner (business value and acceptance criteria), Developer (implementation approach and feasibility), QA Engineer (testability, edge cases, and error scenarios)
- When: During backlog refinement, for every user story before it enters the sprint. Keep sessions short (15-30 minutes per story) and focused
- What to discuss: What exactly is the expected behavior? What are the edge cases? What happens when things go wrong (invalid data, network errors, concurrent access)? How will we know it's done? What non-functional requirements apply?
- Output: BDD scenarios (Given/When/Then) that all three agree on. These become acceptance criteria, test cases, and developer implementation targets simultaneously
- Common resistance and response: 'We don't have time for this.' Counter: 'Three Amigos takes 30 minutes per story. The average defect found in testing takes 2 hours to fix plus 1 hour to retest. If Three Amigos prevents 2 defects per story, it saves 4 hours per story. Net gain: 3.5 hours per story'
Tip
Tip
Practice Pair Testing and Three Amigos Sessions in small, isolated examples before integrating into larger projects. Breaking concepts into small experiments builds genuine understanding faster than reading alone.
Practice Task
Note
Practice Task - (1) Write a working example of Pair Testing and Three Amigos Sessions from scratch without looking at notes. (2) Modify it to handle an edge case (empty input, null value, or error state). (3) Share your solution in the Priygop community for feedback.
Quick Quiz
Common Mistake
Warning
A common mistake with Pair Testing and Three Amigos Sessions is skipping edge case testing - empty inputs, null values, and unexpected data types. Always validate boundary conditions to write robust, production-ready qa engineering code.
Key Takeaways
- Pair testing and Three Amigos are structured collaboration techniques that combine multiple perspectives to produce better quality outcomes than any individual working alone.
- Who: Product Owner (business value and acceptance criteria), Developer (implementation approach and feasibility), QA Engineer (testability, edge cases, and error scenarios)
- When: During backlog refinement, for every user story before it enters the sprint. Keep sessions short (15-30 minutes per story) and focused
- What to discuss: What exactly is the expected behavior? What are the edge cases? What happens when things go wrong (invalid data, network errors, concurrent access)? How will we know it's done? What non-functional requirements apply?