Testing Quadrants refer to a framework introduced by Brian Marick to categorize different types of software testing based on their purpose and audience. This model helps teams balance testing efforts across different perspectives.
The Four Testing Quadrants:
1.Quadrant Q1 (Technology-facing, Supports Development)
- Type: Unit tests, Component tests
- Purpose: Ensures that code works as expected at a low level.
- Tools: JUnit, NUnit, TestNG, etc.
2.Quadrant Q2 (Business-facing, Supports Development)
- Type: Functional tests, Story tests, Prototypes, Simulations
- Purpose: Ensures that business logic meets requirements.
- Tools: Selenium, Cucumber, FitNesse, etc.
3.Quadrant Q3 (Business-facing, Critique Product)
- Type: Exploratory testing, User acceptance testing (UAT), Scenario testing
- Purpose: Validates the user experience and business value.
- Tools: Manual testing, User feedback, Beta testing.
4.Quadrant Q4 (Technology-facing, Critique Product)
- Type: Performance testing, Security testing, Load testing
- Purpose: Evaluates non-functional requirements (NFRs) like performance, security, and scalability.
- Tools: JMeter, LoadRunner, OWASP ZAP, etc.