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.
No account needed · Scored in under a minute against a senior rubric
What does Agile Testing Quadrants mean in practice?
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 do interviewers ask about Agile Testing Quadrants?
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.
What does Agile Testing Quadrants look like in a real project?
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.
How should you talk about Agile Testing Quadrants in an interview?
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.
Go Deeper on Agile Testing Quadrants
Know the term. These are the courses that turn the concept into something you can demonstrate.
Common questions about Agile Testing Quadrants
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.
Which terms relate to Agile Testing Quadrants?
Explore related glossary terms to deepen your understanding.
Related Resources
Dive deeper with these related interview prep pages.
Free QA career tools, no account needed
Instant and private, everything runs in your browser. Try them before you sign up.
QA Resume Checker
Instant 0-100 score on automation keywords, impact, and ATS formatting.
QA Cover Letter Generator
A tailored 3-paragraph QA cover letter from your resume and a job post.
QA Application Tracker
Drag-and-drop kanban to track every QA application from Applied to Offer.
QA Take-Home Test Generator
A realistic take-home assignment with a scenario, tasks, and a rubric.
QA LinkedIn Headline Generator
A recruiter-searchable headline, About section, and skills list.
QA STAR Story Builder
Structure a QA behavioral answer with the STAR method and instant checks.
QA Bug Report Generator
Build a clean, reproducible bug report for Markdown, Jira, or plain text.
Boundary Value Analysis Generator
Generate boundary value and equivalence partitioning test cases from a range.
QA Metrics Calculator
Calculate DRE, defect leakage, defect density, and pass rate with interpretation.
QA Test Plan Generator
Build a structured test plan (scope, approach, criteria, risks) in Markdown.
QA Salary Calculator
Estimate QA, SDET, and automation tester pay by level, market, and skills.
QA Offer Evaluator
See total comp, a counter range, and a ready-to-send negotiation message.
Ready to Ace Your QA Interview?
Practice explaining agile testing quadrants and other key concepts with our AI interviewer.
Join 500+ QA engineers already practicing with AssertHired.
A test passes locally but fails in CI about one run in five. Walk me through what you check first, and why.
Scored on the same four dimensions as the real thing: Technical accuracy · Coverage · Clarity · Best practices.
Rather skip ahead? Create a free account