-
-
- Obtain a copy of the Requirements Report, FRAM document, Database Design Report, and Detailed Design Report.
- Determine a table of contents for the system test plan and assign the individual test plan scenarios to testers.
- Inform QA and publishing of delivery dates for QA review and publishing. Inform QA of any special testing strategies which will be adopted.
- Review the above-mentioned documents for the test plan scenarios to be written.
- Schedule a testing overview with the analysis and/or development teams to gather the necessary information for writing the test plan scenario.
- Determine the test cases for the test plan scenario.
- Allocate the FRAM to the appropriate test case.
- Write the test plan scenario using the system test plan template.
- Submit a copy of the test plan scenario to the appropriate parties (Analysis and Development teams) for review. The appropriate parties include a System Test peer and development. Depending on the project, the client may participate in a system testing role and may also review the test plan scenario prior to publication.
- Submit a copy of the allocated FRAM to test plan/test case to the FRAM officer. Obtain an updated FRAM document allocated to test plan/test case.
- Submit a copy of the test plan scenario which has been reviewed in a previous step to QA. Along with the test plan scenario, submit a copy of the FRAM which has been allocated to test plan/test case level.
- Upon QA review, make any updates to the test plan scenario which are deemed appropriate.
- Resubmit the test plan scenario to QA for final review.
- Submit the test plan scenario to publishing.
- Create the System Test Tracking Report once all test plan scenarios have been reviewed by QA.
- Submit the System Test Tracking Report to Publishing
- Obtain a copy of the Requirements Report, FRAM document, Database Design Report, and Detailed Design Report.
-
Leave a Reply
You must be logged in to post a comment.