The Agile Testing Quadrants (from Brian Marick / Lisa Crispin & Janet Gregory) are a model that organizes tests along two axes — business-facing vs technology-facing, and supporting-the-team vs critiquing-the-product — into four quadrants, helping teams ensure balanced test coverage rather than over-focusing on one kind.
The four quadrants are: Q1 (technology-facing, supporting the team) — unit and component tests that guide development; Q2 (business-facing, supporting the team) — functional tests, acceptance tests, examples/BDD that confirm the right thing is built; Q3 (business-facing, critiquing the product) — exploratory testing, usability, and user-acceptance that probe the product from the user's view; Q4 (technology-facing, critiquing the product) — performance, security, and reliability testing. 'Supporting the team' tests are typically automated and guide building the product right; 'critiquing the product' tests often involve human insight or specialized tools and probe for problems in the finished product. The model's value for QA is as a coverage checklist: teams frequently over-invest in Q1/Q2 automation and neglect Q3 exploratory or Q4 non-functional testing. Referencing the quadrants in an interview shows you think about a balanced, whole-product test strategy, not just automated functional checks.
A team with strong unit (Q1) and automated functional (Q2) coverage keeps shipping features that are technically correct but confusing to users and occasionally slow under load. Mapping their coverage to the quadrants reveals they've neglected Q3 (exploratory/usability) and Q4 (performance), so they add exploratory sessions and load tests to close the gap.
| Quadrant | Examples | Purpose | Typical Mode |
|---|---|---|---|
| Q1 — Technology-facing, Supporting | Unit tests, component tests, integration tests | Guide development; build the product right | Automated |
| Q2 — Business-facing, Supporting | Functional tests, acceptance tests, BDD examples, prototypes | Confirm the right thing is being built | Automated + manual |
| Q3 — Business-facing, Critiquing | Exploratory testing, usability testing, UAT | Probe the product from the user's perspective | Manual / human insight |
| Q4 — Technology-facing, Critiquing | Performance, load, security, reliability testing | Verify non-functional quality attributes | Specialized tools |
Scenario: A team proudly reports 85% automated test coverage and a green pipeline, yet users complain the app is confusing and it recently fell over during a traffic spike. Using the Agile Testing Quadrants, how do you explain the gap and what would you add?