Software Test Plan Process
6 October 2011
Here is the Process of Software Test Plan:
- Determine the demands to be tested. All test cases should be obtained using the actual Specification of Design.
- Define which particular test(s) you schedule to apply to test each part.
- Revise the test data and test cases to be convinced that the application has been accurately tested and that the test data and test cases are appropriate to examine proper operation of the application.
- Define the anticipated results which you are going to get for every test.
- Fill in the documentation the test case conformation, test data, and anticipated results. This data should be applied on-line Test Case Design (TCD) and registered in the unit's Software Development File. A successful Peer Technical Review baselines the TCD and make the base of coding.
- Execute the test(s).
- Fill in the documentation the test data, test cases, and test conformation applied in test work. This data should be applied on-line Unit/System Test Report and saved in the unit's Software Development File.
- Successful unit testing is necessary before the unit is entitled to receive the integration of components/system testing.
- Unsuccessful software testing need a Program Trouble Report to be created. This document should report about the test case, the emerged trouble, its potential reason, and the steps that lead to the emergence of the problem. It should be applied as a basis for further technical analysis.
- Test documentation and reports should be applied on-line. Any technical requirements need to be discussed, reexamined, or updated and should be processed without delay.
- Test Case Design
- Problem Trouble Report (if any)
- System/Unit Test Report