Test plans in Agile
One of the benefits of Agile is to be able to continuously change and improve the solution quickly to respond to customer and environment needs. This notion can make it very difficult for carrying out a test plan. Agile embraces change therefore a static test plan may not be sufficient. There are four quadrants to testing in Agile.
- Quadrant 1 – Is technical specific, this is where we see unit testing, and integration testing. This quadrant helps the team to find issues themselves and self-improve before moving an item to a tester. This increases the confidence in the code provided that it at least does what is meant to do.
- Quadrant 2 – This is a functional specific quadrant which allows testing of the requirements as they were specified.
- Quadrant 3 – One of the best ways to get the most of your product is to pass it to someone to run some exploratory testing with it. This exploratory testing does not limit them on what they should and should not look at. They just use the solution. This is where the benefit of user experience is realised.
- Quadrant 4 – There are two important things we want to achieve in testing. The solution needs to meet both business and technical needs. This is where we ensure that our non-functional needs are met, such as performance and security.
The quadrants not only help us in planning the tests but they help us identify which types of tests needs to be executed. The test strategy needs to consider ALL these quadrants.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: