Overview <The overview functions as the summary” of the test plan: its goals, its scope, and its “executive schedule. This should be kept brief, as you will go into further detail in subsequent sections of the test plan.> Scope <Your scope should define, in general terms, the methods that will be used in the testing process and the projected results. The scope should also include the most critical performance measures, as well as a list of what the test plan will not address, and why.> Objectives <Your test plan should clearly define what you will test and why you will test it. These should always be based on industry standards. Determine what the scope of the test is. What scenarios will be tested? Determine what is out of scope for the test. What scenarios will not be tested? Common scenarios include Module/Unit Testing, Integration Testing, Systems Testing, Acceptance Testing, and Beta/Pilot Testing.> Strategy <This section outlines the overall test strategy for your test plan. It will include any project strategy that impacts the testing (i.e. phased approach, pilot, etc). It will specify the rules and processes that will apply to the tests. Include information on tools to be used, what metrics will be collected and at what level, how many configurations will be tested, and whether there are any special requirements or procedures for testing.> Success Criteria <This section outlines the success criteria for your testing effort. Testing success criteria are the standards by which the test effort will be judged successful. In this section document how each objective or goal will be met. Include the acceptance criteria from the business/program areas required to obtain signoff approval for implementation.>
Overview <The overview functions as the “executive summary” of the test plan: its goals, its scope, and its schedule. This should be kept brief, as you will go into further detail in subsequent sections of the test plan.> Scope <Your scope should define, in general terms, the methods that will be used in the testing process and the projected results. The scope should also include the most critical performance measures, as well as a list of what the test plan will not address, and why.> Objectives <Your test plan should clearly define what you will test and why you will test it. These should always be based on industry standards. Determine what the scope of the test is. What scenarios will be tested? Determine what is out of scope for the test. What scenarios will not be tested? Common scenarios include Module/Unit Testing, Integration Testing, Systems Testing, Acceptance Testing, and Beta/Pilot Testing.> Strategy <This section outlines the overall test strategy for your test plan. It will include any project strategy that impacts the testing (i.e. phased approach, pilot, etc). It will specify the rules and processes that will apply to the tests. Include information on tools to be used, what metrics will be collected and at what level, how many configurations will be tested, and whether there are any special requirements or procedures for testing.> Success Criteria <This section outlines the success criteria for your testing effort. Testing success criteria are the standards by which the test effort will be judged successful. In this section document how each objective or goal will be met. Include the acceptance criteria from the business/program areas required to obtain signoff approval for implementation.>
Test%20Plan%20Template.docx