6.4Quadrant 3: Exploratory and Usability Testing (Business-Facing, Critiquing the Product)

What It Includes

• Exploratory testing (creative, unscripted investigation)
• Usability testing (is it easy to use?)
• User acceptance testing (UAT)
• Alpha and beta testing
• Accessibility testing (manual review)

Characteristics

• Manual by design: Automation cannot replace human creativity and judgment
• Continuous during sprint: Not just at the end
• QA and user-driven: QA explores, users validate
• Finds unknown unknowns: Discovers issues nobody thought to write a test for

QA's Role in Q3

• Conduct structured exploratory testing sessions
• Identify usability issues that automated tests miss
• Coordinate UAT with business stakeholders
• Test edge cases, error recovery, and unusual user paths

Exploratory Testing Session Structure

Session Charter: "Explore the new checkout flow focusing on error recovery"
Duration: 60 minutes
Focus areas:
  - What happens when payment fails?
  - What happens when the user navigates away mid-checkout?
  - What happens with slow network?
  - What happens when the session expires during checkout?

Findings:
  - Bug: Back button after payment failure shows empty cart (SHOP-891)
  - Bug: No timeout message when payment API is slow (SHOP-892)
  - Observation: Error messages use technical language ("HTTP 500") instead of user-friendly language
  - Suggestion: Add a progress indicator during payment processing

Why Q3 Cannot Be Automated

Automated tests verify known, expected behavior. Exploratory testing discovers unknown, unexpected behavior. A robot does not wonder "what if I paste an email address into the phone number field?" or notice that the checkout button is barely visible on a dark background. Human intuition and creativity are irreplaceable in Q3.