Example Test Plan: Start Date End Date Network Build (Setup) Testing Date

Example Test Plan
Start Date End Date

Network Build (Setup)
Testing Date
Table of Contents
ATTENDEES......................................................................................................................3
2
Attendees
Name Company Position
3
Introduction
An introduction to the testing explaining briefly what the purpose of the test is, and what should
be observed. Include a brief description of testing goals. List all tests you intend to run.
For example:
The purpose of this prototype is to demonstrate how the individual access layer VLANs can be configured
to separate traffic from the end-devices, IP telephones, and video cameras. The intent is to demonstrate
that computers on VLAN 2 cannot access devices on the voice or video VLANs unless expressly granted
permission.
• Test 1: Baseline Connectivity Test

• Verify physical and IP connectivity between devices on the prototype network.
• Collect operational baselines.
• Demonstrate IP connectivity between devices on the same VLANs.

• Demonstrate lack of IP connectivity between devices on different VLANs.
• Test 2: VLAN Routing Test
• Demonstrate routing of traffic between separate VLANs, unrestricted.
• Demonstrate routing of traffic between separate VLANs with restrictions.
• Simulate traffic and compare to baselines.
4
Equipment
List all of the equipment needed to perform the tests. Be sure to include cables, optional
connectors or components, and software.
Qty. Req Model Any additional Substitute IOS Software

options or Rev.
software required
2 2960 Layer 2 none Any 2950 or 12.2 or above
switch 2960 model
switch
2 37xx multilayer none Any 12.2 or above
switch multilayer
switch or
router with
minimum 2
FastEthernet
ports.
2 Personal FastEthernet At least one Windows, MAC
Computer end- NIC PC and any or Linux
devices other IP end- operating
device system.
(camera,
printer, etc.)
6 Cat 5 or above none none n/a
straight-
through patch
cables.
4 Cat 5 or above none none n/a
cross-over
patch cables
5
6
Design and Topology Diagram
Place a copy of the prototype network topology in this section. This is the network as it should be
built to be able to perform the required tests. If this topology duplicates a section of the actual
network, include a reference topology showing the location within the existing or planned
network. Initial configurations for each device must be included in the Appendix.
Figure 1: Topology - Prototype test topology.

Add a description about this design here that is essential to provide a better understanding of the
testing or to emphasize any aspect of the test network to the reader.
7
For each test to be performed state the goals of the test, the data to record during the test, and the
estimated time to perform the test.
Test 1. Description: Baseline Connectivity Test
Goals of Test:
The goal of the baseline is to verify that the topology is up and running with
the proper protocols and features.
Data to Record:
Configurations
Routing Tables
CPU & Memory
Ping Test Output
Estimated Time:
120 minutes
Test 1. Procedures:
Itemize the procedures to follow to perform the test.
1. Console into one of the devices in the topology and ping all of the other devices in the topology.
Record any anomalies.
2. Start a log file and get the “show running-config”, “show ip route”, “show processes
cpu sorted”, “show processes cpu history” and the first few lines of “show memory”
(should we be using short cuts here or the full syntax?)
3. Telnet to all of the other devices and get the same information.
4. Start baseline traffic and use the “show interface” and “traceroute” commands to verify
that the traffic is taking the correct routes through the network.
5. Test IP connectivity between host devices on the same VLAN.
6. Test IP connectivity between host devices on different VLANs.
8
9
Test 1. Expected Results and Success Criteria:
List all of the expected results. Specific criteria that must be met for the test to be considered a
success should be listed. An example of specific criteria is: “A requirement that ping response
times cannot exceed 100 ms.”
1. All networking devices are connected and accessible through Telnet.
2. Hosts on a VLAN can ping successfully to other hosts on the same VLAN.
3. Hosts on different VLANs are unable to ping successfully.
10
Test 1. Results and Conclusions
Record the results of the tests and the conclusions that can be drawn from the results.
11
Appendix
Record the starting configurations, any modifications, log file or command output, and any other
relevant documentation.
12

Example Test Plan: Start Date End Date Network Build (Setup) Testing Date

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

Example Test Plan: Start Date End Date Network Build (Setup) Testing Date

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Example Test Plan: Start Date End Date Network Build (Setup) Testing Date

Uploaded by

Copyright:

Available Formats

Example Test Plan

Start Date End Date

• Test 1: Baseline Connectivity Test

• Collect operational baselines.

• Demonstrate IP connectivity between devices on the same VLANs.

• Test 2: VLAN Routing Test

• Demonstrate routing of traffic between separate VLANs, unrestricted.

• Demonstrate routing of traffic between separate VLANs with restrictions.

• Simulate traffic and compare to baselines.

Qty. Req Model Any additional Substitute IOS Software

Figure 1: Topology - Prototype test topology.

Test 1. Description: Baseline Connectivity Test

1. All networking devices are connected and accessible through Telnet.

3. Hosts on different VLANs are unable to ping successfully.

You might also like