Creating a Network Test Plan
To prepare a plan to test the network. The plan defines the scope, approach, criteria, schedule, responsibilities, resources, and procedures.
Define the objectives of the test by identifying the areas of the network to be tested including:
Â· Volume Testing. Ensures that the network operates smoothly when subjected to production volumes of data over long periods of time.
Â· Stress Testing. Ensures that the network operates smoothly when subjected to the maximum load expected in production, all at one time. A good rule of thumb is to subject the network to 25 percent more data and processing than is expected during peak loads.
Â· Recovery Testing. Ensures that backup and recovery procedures are working properly.
Â· Security Testing. Verifies that the network meets the security requirements.
Â· Performance Testing. Verifies that performance criteria are met (e.g., response times).
Define Acceptance Criteria
For each test objective, define the criteria for successful completion. For example:
Â· All expected results are achieved on the initial run.
Â· All severe, and high priority faults are corrected and the associated test(s) rerun successfully.
Â· A documented plan is put in place specifying how and when outstanding low and medium priority faults will be resolved.
Identify the high-level activities and tasks together with expected start and completion dates.
Identify the individuals who will be involved in the test and their roles and responsibilities.
Identify the staff, hardware, and software requirements. Confirm that the Network Deployment Plan has accounted for these requirements and resolve any differences.
Define the procedures to be followed in preparing the test cases, preparing test scripts, preparing the test environment, conducting tests, and verifying test results.
Tips and Hints
Document any assumptions made while preparing the plan.
Plan to use automated test tools wherever possible to significantly reduce the testing effort and duration. Automated test tools can be used to generate and apply an adequate number of transactions to facilitate stress and performance testing.