Contingency plan in test plan in software testing

The article about contingence plan in test plan in software testing, it helps you to increase your awareness about test plan contents and required things.

Contingency plan in test plan in software testing


Define the extent of the test and exactly what the test environment will include. Is the test strictly local or does it involve other facilities?


Define the type of disaster that test will simulate and what tools and functions are to be considered damaged or not available.

Test Objectives:

List the objectives for the test. Objectives will be used for planning and evaluating the test. A common objective is to provide training to team members to familiarize them with the facility’s contingency Plan.

Test Start and End Time:

End User Impact:

Identify any affected end users (some systems may be unavailable for normal operations, such as processing claims) and assess any impact on normal facility operations.


Define the actual risks of conducting the test, including the worst case scenario (the worst possible actual impact on the users such as Adjudication Officers) if the execution of the contingency plan during the test is a total failure. Make sure that everyone understands that no test is a failure if lessons are learned (and applied) from it.


Decide what is required to return to normal operations. Include all notifications and actions that must be performed whenever the test is completed or halted.


Test Review: Mention a date, time, and place for the post-test review.

Director’s Approval Signature Block.

These above things are very important in contingence plan in test plan in software testing.

Test Evaluation Report Format

Test Evaluation Report should be prepared following the post-test review. The basic purpose is to document the lessons learned from conducting the test. The Test Evaluation Report should provide information for updating the facility contingency plan and making it a more effective document. The following is a suggested format. Each evaluation report should be tailored to the specific test conducted.

Contingency Plan Test Conducted Date


  1. Report Date:
  2. Brief Test Description:
  3. Evaluation of the Test: Did the test go as planned? Were the objectives met? If not, explain. What were the lessons learned?
  4. Recommendations for Changes to the Contingency Plan:
  5. VACO Recommendations: Recommendations for VBA VACO to incorporate into VBA Directives, Handbooks, Guidelines, and strategies.
  6. Signature Block for Contingency Planning Coordinator:
  7. Director’s Approval Signature Block:

Soon I will publish next information about contingence plan in test plan in software testing and definitely it helps you


Share This Post

One Comment - Write a Comment

Post Comment