Agile testing quadrants is consider to be a tool or a manual, designed by the Brain Marick, which divides the whole agile testing methodology into four basic quadrants. Agile Testing Quadrants help the whole team to communicate and deliver a high quality product in no time. With the help of Agile Testing Quadrants the whole testing process can be explained in a very easy to understand language and the whole team can effectively work on the product.
These Quadrants are:
- Quadrant 1: Technology-facing tests that support the team
- Quadrant 2: Business-facing tests that support the team
- Quadrant 3: Business-facing tests that critique the product
- Quadrant 4: Technology-facing tests that critique the product
The quadrant numbering system does NOT imply any order. You don’t work through the quadrants from 1 to 4, in a waterfall style. It’s just an arbitrary numbering.
- Quadrant 1 consists of all the test cases that are technology driven. These are performed in order to support the team.
- Developers involvement is very important in this quadrant as quality of code is the main focus here.
- Quadrant 1 is associated with Automated testing, and covers the tests such as Unit tests, Component test, API tests and Web Services testing.
- Instant feedback is obtained in this quadrant so that quality of code can be improved easily.
- This quadrant helps to improve the design of the product without affecting its functionality.
- Quadrant 2 consists of all the test cases that are business driven and are performed to support team as well as the costumers.
- Most of the projects working starts from this quadrant.
- The main focus of this quadrant is on the business requirements.
- The tester is greatly involved with the customer to gather the requirements in order to build test cases accordingly.
- Quadrant 2 is associated with Functional testing, story testing, prototypes & simulations and pair testing.
- In this quadrant both manual and automated testing is involved to work on business requirements easily.
- Quadrant 3 consists of all the test cases that are business driven and are performed to Critique the product.
- The main focus of this quadrant is to provide feedback to the Quadrant 1 and Quadrant 2.
- Manual testing based on tester logical thinking, intuitions and user requirements is done to evaluate the application.
- Quadrant 3 is associated with Pair testing with customers, Exploratory Testing, Usability Testing, User Acceptance Testing, Collaborative Testing and alpha & beta testing.
- Quadrant 4 consists of all the test cases that are technology-driven and are performed to critique the product
- Quadrant 4 focus mainly on the non-functional requirements such as performance, security, stress, maintainability, stability etc.
- This quadrant is responsible to deliver the final product to the customer.
- This quadrant is associated with performance testing, load testing, stress testing, maintainability testing, infrastructure testing, data migration testing, security testing, reliability testing, recovery testing and many more.
Attention reader! Don’t stop learning now. Get hold of all the important DSA concepts with the DSA Self Paced Course at a student-friendly price and become industry ready.
- Difference between Agile Testing and Waterfall Testing
- Agile Software Testing
- Difference between Agile and Scrum Testing
- Difference between Agile and DevOps
- Estimation Technique in Agile
- Agile Software Process and it's Principles
- Agile Methodology Advantages and Disadvantages
- Techniques to be an awesome Agile Developer (Part -1)
- Difference between Traditional and Agile Software Development
- Software Engineering | Agile Development Models
- Load Testing Basics, Tools & Practices in Software Testing
- Software Engineering | Differences between Sanity Testing and Smoke Testing
- Difference between System Integration Testing (SIT) and User Acceptance Testing (UAT)
- Software Engineering | Comparison between Agile model and other models
- Difference between Functional Testing and Implementational Testing Approach
- Difference between Database Testing and Data warehouse Testing
- Software Engineering | Comparison between Regression Testing and Re-Testing
- Difference between Scrum Testing and V-Model Testing
- Difference between Positive Testing and Negative Testing
- Difference between System Testing and Integration Testing
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to email@example.com. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.