Atlas › 20 Agile & Scrum › Agile Test Quadrants☰ Read as one page
Agile Test Quadrants
6.1The FrameworkBrian Marick's agile test quadrants organize testing activities by two dimensions: business-facing vs technology-facing, and supporting the…6.2Quadrant 1: Unit and Integration Tests (Technology-Facing, Supporting the Team)- Unit tests - Component tests - Integration tests - API tests6.3Quadrant 2: Functional and Story Tests (Business-Facing, Supporting the Team)- Functional tests (verifying acceptance criteria) - Story tests (automating user stories) - Prototypes and mockups for verification - BDD…6.4Quadrant 3: Exploratory and Usability Testing (Business-Facing, Critiquing the Product)- Exploratory testing (creative, unscripted investigation) - Usability testing (is it easy to use?) - User acceptance testing (UAT) - Alpha…6.5Quadrant 4: Performance, Security, and Load Testing (Technology-Facing, Critiquing the Product)- Performance testing (response times, throughput) - Load testing (behavior under heavy traffic) - Stress testing (behavior beyond expected…6.6Balancing the Four QuadrantsThe key insight: all four quadrants are necessary. Teams that only automate Q1 tests miss business-level gaps. Teams that only do Q3…6.7Hands-On Exercise1. Map your current testing activities to the four quadrants. Which quadrants are well-covered? Which are neglected? 2. Identify one…