Test Automation Entry and Exit Criteria

Test Automation Entry/Exit Criteria : Test Automation Entry/Exit Criteria Author – Mr. Ashish Abrol Email – ashish.abrol@grailtest.com Web – www.grailtest.com

Entry Criteria : Entry Criteria Frequent builds/ patches/iterations to the existing application necessitate several iterations of testing which includes this test case. (For example Smoke test/Regression tests) Test cases that need verification with a high precision Test case needs to be executed for large and diverse data sets Manual test cases which are tedious/repeatable/ time consuming (For example complex calculations etc.) Test case functionality should be complex and not very simple like Login/Logoff scripts

Exit Criteria : Exit Criteria Individual Script has been executed successfully with no unexpected debug messages OR message boxes Script has been reviewed for coding standards Review completed for indentation and comments for variables, functions, test steps etc. Script and required test artifacts (For example Data sheet, Object repository, application functions etc.) have been version controlled with proper label Automation script is added to the respective test set in test management tool

Test cases to be Discarded : Test cases to be Discarded Scenarios which reflect Random testing or Ad hoc testing Script has been reviewed for coding standards Test case which needs Manual Intervention One time test cases which will not be executed in future execution cycles Scenarios which involve testing based on Intuition Test cases which test the Usability of the application

Slide 5 : Thank You!