Test Phase Checklist

The test phase checklist is a general guide for users to gauge the quality of product build delivery before starting tests in system test (ST) or RAT. Further, tailoring can be done to align the checklist with any specific product.

Intended for

• Release owners
• Product owners
• Scrum masters
• Software Engineers
• Hardware Engineers
• Test Engineers
• Quality Engineers

Checklist for start of System Test (ST)

• The product/s have all the scope epics/features in a resolved state as per acceptance criteria.
• Tests for Features and User Stories have been performed, and the quality is at an acceptable level for starting System tests.
• System is installable without any blocker. For any not fixed blocker, a workaround exists.
• All the bugs with critical severity have been investigated and corrected.
• All the bugs with high severity have been analyzed, a workaround (if applicable) exists, and a plan for all such bugs is available.
• All the reported crashes/hang issues are described clearly, and a plan for all such bugs is available.
• A declining trend for reported bugs is presented.
• Product/s have been successfully integrated into an SI system.
• Non functional tests are executed in the SI system.
• Draft version of user manuals is available. One round of review with Product Management is completed.
• Test cases are written, reviewed, and approved.
• Test applications are available.
• Test environment documents are created, reviewed, and approved.

Checklist for start of Release Acceptance Test (RAT)

• All the tests are completed in Product Test (PT) and System Test (ST), including the "conclusion of test" report.
• Results from early long-time tests have been analyzed, and bugs are reported.
• Installation and start-up of products work without problems.
• No critical or high open bugs exist.
• No crashes or serious problems have been reported in the last tested build.
• Medium or low severity bugs have been discussed, and a decision exists on handling.
• No build change is planned due to pending medium or low bugs.
• User Documentation: The installation guide and the user manuals for all products are approved.
• Release Notes for user documentation are drafted and reviewed with the technical team.