What is Agile Testing Quadrants?

The agile testing quadrants are a model (popularized by Brian Marick and Lisa Crispin and Janet Gregory) that organizes testing activities along two axes, business-facing vs technology-facing, and supporting the team vs critiquing the product, producing four quadrants that together ensure balanced test coverage.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

IN DEPTH

In depth.

The model maps testing into four quadrants. Q1 (technology-facing, supporting the team): unit and component tests, automated, guiding development. Q2 (business-facing, supporting the team): functional tests, examples, story tests, prototypes, often automated, defining what to build. Q3 (business-facing, critiquing the product): exploratory testing, usability testing, user acceptance, mostly manual, evaluating the real experience. Q4 (technology-facing, critiquing the product): performance, security, reliability, and other non-functional tests, often tool-driven.

The value of the model is balance and communication. It reminds teams that automation (Q1/Q2) and human evaluation (Q3) both matter, that non-functional quality (Q4) is not optional, and that tests serve different purposes, some support building the right thing, others critique whether the built thing holds up. It is a planning and conversation tool, not a strict process: teams use it to check they are not neglecting a whole category (for example, leaning entirely on automated functional tests while ignoring exploratory or performance testing).

The quadrant numbers are not an execution order, they are categories. Q1 and Q2 (supporting) tend to be automation-friendly; Q3 leans manual and exploratory; Q4 needs specialized tools.

WHY IT MATTERS

Why interviewers ask about this.

The agile testing quadrants come up in interviews about test strategy and agile QA. Using the model to argue for balanced coverage, automation plus exploratory plus non-functional, demonstrates strategic thinking about a whole testing approach rather than a single technique.

EXAMPLE

Example scenario.

Planning testing for a new feature, a team uses the quadrants as a checklist: unit tests (Q1) and automated story tests (Q2) guide development, an exploratory session and a quick usability check (Q3) evaluate the experience, and a performance and security pass (Q4) covers non-functional risk, ensuring no category is forgotten.

TIP

Interview tip.

Describe the agile testing quadrants by the two axes (business vs technology facing; supporting vs critiquing) and give an example test type per quadrant (unit, functional/story, exploratory/usability, performance/security). Frame it as a planning tool for balanced coverage, not an execution order.

FAQ

Frequently asked questions.

What are the two axes of the agile testing quadrants?

One axis is business-facing vs technology-facing (what the test is expressed in terms of). The other is supporting the team vs critiquing the product (whether the test guides building or evaluates the result). Crossing them yields four quadrants covering unit/component, functional/story, exploratory/usability, and non-functional tests.

Are the testing quadrants an order of execution?

No. The quadrant numbers (Q1 to Q4) are categories, not a sequence. The model is a planning and communication tool to ensure balanced coverage across automated, exploratory, and non-functional testing, not a step-by-step process to follow in order.