Services
Platform and Technology Capabilities
Home / Insights / Blog / Exit Criteria in Agile Testing
January 31, 2017 - by Ahesanali Vijapura
Any process-driven software company understands the importance of following a methodical approach for quality assurance. You would probably agree with the need to adopt a systematic approach towards software testing, since it ultimately ensures that the delivered product is of the highest quality standards. According to a rough estimate, the worldwide monetary impact due to software failures is close to $3 trillion annually. For S&P 500 companies alone, the loss due to flawed testing strategy is valued at $100 billion.
Agile testing – weaving testing during the development phase
The agile testing practice is often adopted, which, in simple terms, is testing conducted in real time during the development phase itself. Both the development and QA teams jointly executing the agile testing help avoid the following common issues:
Software testing encompasses four criteria:
1) Entry Criteria, which is the first stage defining the conditions that should exist to begin the testing process 2) Suspension Criteria temporarily suspends the testing process when the test case document is sent for approval 3) Resumption Criteria specifies the conditions when the testing process can resume 4) Exit Criteria, which defines the conditions that must be fulfilled to end the testing process
Transitioning from entry to exit
Entry criteria in STLC (software testing life cycle) is a set of pre-conditions that should have occurred as on-going activities for the testing phase to begin. These pre-conditions can be categorized into two different types:
It is good to note, that the conditions which define entry criteria lay the foundation for exit criteria. In absence of an SRS or a test plan document, it’s difficult to establish exit criteria.
Exit criteria marks the end of alpha testing
It is a question every tester may ask: “when and how does one stop testing?” Even after testing a software code, there is no guarantee that the code is 100% bug-free. There will always be instances where defects may creep in, probably at a later stage or due to a change request. The purpose of testing, however, is not to make the software code 100% bug-free, but to ensure that the code achieves the business objectives and to find the amount of deviation in the results from the intended output. Pre-requisites, also known as exit criteria, for ending the testing process are:
With the above mentioned conditions fulfilled, it is safe to initiate test closure activities. This ensures that the software application successfully meets business objectives.
Exit criteria can be the entry criteria for another stage
The last stage of the Agile STLC (Software Testing Life Cycle) which consolidates all the activities performed during the test life cycle is also known as the test closure activity phase. The objective of this phase is to have an established document for any future reference. The activities include:
Exit criteria in the agile testing practice helps meet the objectives of:
With so much changing with testing tools and processes, it’s hard to resist the benefits you can achieve by properly defining and implementing the exit criteria in an agile STLC. This will help you work your way towards improvement in productivity, and reduction in test maintenance efforts in numerous test engagements.
Blog