Testing and updating the plan
This allows test organizations to plan, acquire or develop test equipment and other resources necessary to implement the test methods for which they are responsible.
Test responsibilities also includes, what data will be collected, and how that data will be stored and reported (often referred to as "deliverables").
Depending on the product and the responsibility of the organization to which the test plan applies, a test plan may include a strategy for one or more of the following: A complex system may have a high level test plan to address the overall requirements and supporting test plans to address the design details of subsystems and components.
Test plan document formats can be as varied as the products and organizations to which they apply.
Suggestions for improving test scenarios, plans, or scripts provided by test participants should be incorporated into the testing cycle.
In the event that tests do not succeed in meeting their required objectives, management should determine whether it is necessary to re-test prior to the next scheduled test.
One outcome of a successful test plan should be a record or report of the verification of all design specifications and requirements as agreed upon by all parties.
IEEE 829-2008, also known as the 829 Standard for Software Test Documentation, is an IEEE standard that specifies the form of a set of documents for use in defined stages of software testing, each stage potentially producing its own separate type of document.
Project planning is one of the pivotal elements in the project management process.
After the test results are executed, evaluated by management, independently assessed, and reported to the board, it may be necessary to update the BCP and test program.
As part of this process, the BCP and test program should be reviewed by senior management, the planning team or coordinator, team members, and the board at least annually.
Test owners, typically business line or support management, should assign responsibility for resolution of material business continuity problems identified during testing and should track issues to ensure that they are effectively addressed in a timely manner.
Issues requiring resolution may stem from a number of factors, including changes in internal or external dependencies involving staff, technology, facilities, and third parties.