Test Readiness Checklist...!

Before starting the actual testing, it is important to check whether the system / project / environment is ready for testing. This is called as Test Readiness Review. It is better to do it with a checklist.

Below is a sample Test Readiness Review Checklist:

1. Whether all the tests are conducted according to the Test Plan / Cases ?

2. Are all problems / defects translated into Defect Reports ?

3. Are all the Defect Reports satisfactorily resolved ?

4. Is the log of the tests conducted available?

5. Is unit testing complete in all respects?

6. Is Integration testing complete ?

7. Is all the relevant documentation baselined ?

8. Is all work products products baselined?

9. Is the test plan baselined ?

10. Does the test plan contain the strategy / procedure to conduct the system test ?

11. Are baselined test designs and test cases ready?

12. Is unit/integrated test software ready ?

13. Is the user manual ready?

14. Is the installation procedure documented ?

15. Are all the product requirements implemented?

16. Is the list of known problems available? Is there any "workaround" procedure for the known bugs ?

17. Are test environment needs met for Hardware, code, procedures, scripts, test tools etc.?

18. List of exceptions in test software and test procedures and their work around if any?

19. Is the test reporting tool is available?

20. Are the designers educated on Test reporting tool?

21. Is any standard methodology / tool used and is appropriate to the type of the project?

22. Is the criteria for regression testing defined? Has the regression testing been done accordingly?

23. Is the source code available from the client for performing regression testing complete in all respects?

24. Is the source code freezed for testing?

Test Readiness Assessment Checklist

For Assessment of:
Agency Name
Project Name
Test Phase
Date

Criteria	Yes / No / NA
a. Is the Test Plan comprehensive and complete?
b. Are the test scenarios, procedures, descriptions, and other test information comprehensive and complete?
c. Have test plan, test scenarios, procedures, descriptions, and other test information been reviewed and approved by the designated approvers?
d. Is documented methodology for the test phase feasible?
e. Is documented methodology for the test phase unambiguous?
f. Was the prerequisite test phase completed successfully?
g. If the prerequisite test phase was not completely successful, have workarounds or contingency plans for proceeding with testing been identified?
h. Was the build verification test on the release to be tested executed successfully?
i. Has the entry criteria for the test phase to be initiated been met?
j. Is the test data available?
k. Has test data been approved by the designated approvers?
l. Is the specified environment operational?
m. Have software, documentation, data, and other appropriate configuration items been placed under configuration control?
n. Are the scheduled resources available to execute and support the test phase activities?
o. Have testing resources participated in test plan reviews, training or orientation?
p. Have testing resources participated in system training or orientation?
q. Are the number and severity of remaining defects within established thresholds?
r. Are there risks associated with initiating the test phase?
s. If there are risks associated with initiating the test phase, are there plans to accept or mitigate those risks?