Agile Testing Quadrants are a visual tool for understanding different QA tests and form the core of an agile testing framework. They differentiate between business- and technology-facing tests, and those that support programming or ‘critique’ the product. Testing types are sorted into these four categories on a grid. Understanding what are agile testing quadrants and how to use them in QA can help teams plan and prioritize testing effectively.
You can use that grid to decide on your QA approach and manage your goals. Additionally, it allows you to communicate clearly and persuasively the purpose of testing types to non-technical stakeholders.
The origins of the 'Marick Test Matrix'
Brian Marick, a software consultant, published an influential series of articles about Agile Testing in 2003. He did so after being told that he was ‘not doing enough to aid the development of Agile testing as a discipline, as a stable and widely understood bundle of skills.’
He aimed to address this criticism, starting with agile testing quadrants. Originally known as the ‘Marick Test Matrix’, these quadrants form a basic grid:
(Hat tip to Brian Marick)
From there, he suggests placements for testing types within each of the four quadrants, and expands on the reasoning behind each choice.
A breakdown of the Agile Testing Quadrants
Since Marick’s original vision, practitioners have created variations of the agile testing framework, adding more information to the grid. These aren’t hard and fast rules, but generally speaking, here’s what each quadrant means:
Q1 – Technology-Facing Unit and Component Tests
Unit and component tests are performed throughout your application’s development. They provide feedback to your developers on the quality of their code on an ongoing basis, usually through repeated, automated processes. These tests are critical in any agile testing framework.
Q2 – Business-Facing Functional Tests
With a combination of manual and automated tests, these ‘business-facing’ tests focus on the customer experience while still supporting your application build. These include functional tests, which ensure the product works as intended. Understanding what are agile testing quadrants and how to use them in QA is essential here.
Q3 – Manual User Acceptance and Exploratory Tests
User Acceptance Tests (UAT), usability, and exploratory testing all belong in this quadrant. These involve manual testing by experienced QA engineers and end-user testing. The goal is to gain feedback and improve product quality, ensuring it is fit for the designed purpose.
Q4 – Technology-Facing Performance and Security Tests
These include performance tests, load testing, and security checks for your application. Many tools can automate this type of testing, such as Selenium alongside JMeter. These tests complete the agile testing framework by ensuring robust, production-ready software.
Where's the value?
This visualization doesn’t dictate prioritization. You don’t necessarily start at Q1 and work your way around. Decisions should be based on requirements, risks, and dependencies.
However, agile testing quadrants provide a holistic overview of QA software testing. They help teams see gaps, plan coverage, and ensure alignment between business goals and technical quality. In this way, what are agile testing quadrants and how to use them in QA helps answer the key question: “Have we covered all the bases?”
The Test Automation Playbook
Read The Test Automation Playbook to build a future-ready QA strategy with insights on tools, tactics, and ROI.
Frequently Asked Questions (FAQs)
What are Agile Testing Quadrants?
Agile Testing Quadrants are a grid-based visualization tool that categorizes tests as business- or technology-facing and supporting programming or critiquing the product.
Why are Agile Testing Quadrants important?
They provide a holistic overview of QA, helping teams prioritize, communicate, and cover all necessary test types.
What is the difference between Q1 and Q2?
Q1 focuses on technology-facing unit and component tests, whereas Q2 emphasizes business-facing functional tests.
How do Q3 and Q4 differ?
Q3 is for manual user acceptance and exploratory testing, while Q4 covers automated performance, load, and security testing.
Are Agile Testing Quadrants still relevant today?
Yes, they remain a valuable visualization tool for planning, communication, and ensuring comprehensive test coverage.
Can Agile Testing Quadrants be adapted?
Absolutely. Modern QA teams adjust the quadrants based on project needs, risk factors, and tool availability.
