The Agile Testing Quadrants Flashcards
What is the Agile Testing Quadrants?
It is a model that categorizes the testing activities etc. into four categories, based on the focus of those activities. Examples are Q1 which contains unit tests is requirement and technology facing, while Q3 which contains UAT and usability tests are business and product faced.
The order of which the quadrants are applied is not strict.
What is Quadrant 1 about?
Q1 is Technology, Requirements, and Automation facing. The activities involve Unit tests and integration tests etc.
These activities measure the internal quality of the code, meaning that it ensures functionality is working as expected.
Because of the unit test etc, it is a lot about guiding early development and continuous feedback.
The tests should always be automated and the Q1 activities are responsible for making the most tests.
What is Quadrant 2 about?
Q2 is Business- and Requirements-facing. The activities are functional tests, prototypes, story tests, and UI tests. This could be called ‘Business-Facing’ tests, as they help validate the features of an application (features meet user needs / business needs).
These activities are often guided by the information (examples) given by the customer and support the team in the requirements identification.
Risks here are that there might be miscommunication between the customer and team flowing requirements.
There are both manual and automated tests in the quadrant.
- Manual: prototypes and mock ups.
- Automated: functional and UI-tests.
What is Quadrant 3 about?
Q3 is Product- (critique) and Business-facing.
The activities are Exploratory testing, Usability Testing, and Use Acceptability Testing.
These activities aim to verify or validate the requirements (business-facing) which also finds faults in the product if those requirements are not met, why it is product faced also.
What is Quadrant 4?
Q4 is Product- and Technology-facing.
The activities involve Performance & Load Testing, Security Testing, and reliability, sustainability, compatibility, and maintainability testing. These things should be automated.
Sum up all the quadrants ‘Facings’
- Techonology
- Requirements and specifications
- Business
- Product critique
