As we know that agile testing is a dynamic and productive type of testing to carry out the testing activities on a regular basis throughout the development process. Testers often remain in the ambiguity with respect to the procedures or approach to perform agile testing in a short duration of iteration along with the development process such as:
Agile testing quadrants may be considered as a tool or a manual outlined by the Brain Marick, which divides the whole agile testing methodology into four quadrants for arranging the testing types to be performed at each different level to suit the agile manifesto.
The working of each quadrant may be seen as under:
This quadrant concerns with the quality of the code and the components, which sees the involvement of developers along with the implementation of the technologies and automation i.e. technology driven test cases to support the team and covers the unit testing and component testing of the system at a unit level.
However, the participation of the developers in the Q1 does not restrict the entry and work of a tester. A tester may go through the documentation work to have a better understanding of the internal structure of the software product which may help in designing, effective test cases.
In the second quadrant, we may see the business driven test cases are being implemented for supporting the team. Basically, the main focus of this quadrant is the business requirements. Generally, it involves the usage of both manual and automated testing and consists of testing types such as functional testing, story tests, prototypes & simulations, pair testing done at the system level.
A tester continuously interacts with the client or the stakeholders to gather and implement the evolved requirements in the test cases.
In the third quadrant, feedbacks and reviews of previous testing phase or quadrants along with the real user experience, work as a driving force to test the software product, using multiple scenarios. The Manual testing method is being used to evaluate the software application based on the user requirements and logical thinking of a tester. This quadrant is used to build and gain confidence in the usability of the product.
This quadrant involves the usage of the technology i.e. tools, to automate the process of evaluating the software product at an operational acceptance level to fulfill the non-functional requirements, such as reliability, security, compatibility, maintainability, interoperability, recovery, etc.
The testing types covered under this quadrant consist of performance testing, load testing, stress testing, maintainability testing, security testing, reliability testing, recovery testing and other types of testing, used to verify and validate the non-functional requirement of the software product.
Some of the commonly used tools in the Q4 are Jconsole, Loadrunner, JMeter, etc.
Note: It is pertinent to mention that there is no hard and fast rule, to follow the quadrants in a sequential manner as explained above. A tester may start from any of the quadrants as per the requirements, priority, risks involved, and its own choice.