Software Testing Entry and Exit Criteria

Before entering or exiting the software testing phase, testing team should make sure that the corresponding Test Entry or Exit criteria mentioned in the Test Strategy or Test Plan has been met. It’s a very important step in the Testing Life Cycle as it helps in the implementation of the testing processes. I’ve seen companies not even aware of such practice and those who know don’t follow it properly.

The Test Entry/Exit criteria could differ from company to company but the basic idea is same to facilitate the testing by making sure everything is available and as per the expectations.

For example, System Testing Test Entry criteria covers areas like,

• Evidence of the successful unit testing  


• All components are ready for testing


• Test Environments availability


• Smoke Testing


• Test Documents

Similarly, Test Exit criteria makes sure to assess the following,

• All planned testing successfully completed.


• No critical, high severity defects open


• Test Summary Report approved


• Any outstanding defects have been risk-assessed.

There would be scenarios where these criteria won’t meet and in that case an agreement has to be reached between the project stakeholders whether to move ahead or wait for the completion of the pending items.

Follow and Like us:

Software Testing Entry and Exit Criteria