Test Case Checklist

Test case audit checklist.

SL no.	Checklists
1	There should be two different test plan , one for test case lifecycle grooming (Test Pool) and another for recording execution (Test Lab).
2	All test cases must have Actions and Expected results defined in Steps.
3	During execution all test cases must be in "READY" state, no test cases should be in "Design" state. Only for first execution, it can be in "Design" state unless final review and approval is completed but from next round it should be set as "READY".
4	If test cases are in "READY" state, it means test cases are reviewed and Review Summary field must contain review comments , reviewer and implementation status @ TEST LAB.
5	The Test Type field should not be blank and must be assigned with the correct test type value.
6	The Priority must be set after review with PO. For STT, we will find some mechanism to prioritize & evaluate.
7	The Regression field must be set as true for all use cases that are passed in the last execution and planned for re-execution in the current build.
8	The Description field must contain the intention of the test cases and pre-conditions. If necessary reference document can be also attached.
9	All test cases must be linked with epics / features / user stories (possible in both ways direct linking or through a requirement-based test suite)
10	All failed test cases must be linked with affecting bug (Affected By with the test case WI).
11	A requirement-based test suite should be used for all new feature testing. For SIT/STT level, Hybrid model can be used where it can be combination of Requirement-based and Static suites.
12	Marking test cases as Passed / Failed must be on step level, not only on test case level.
13	Test Environment must be set for test cases before execution.
14	Automated test cases should have Automation Date, Automated by, and Automation status fields set properly.
15	Test Conclusion must be well documented which should provide basic information about the product/system under test, quality observations, bug validation, etc.
16	For SIT/STT, the actual result should be captured for all test steps during execution. Automated test cases should be granular.