Load And Performance Test Plan Page 8
ADVERTISEMENT
1
2
3
4
5
6
7
8
9
10
11
12
13Project Name Test Plan
environment is production-like or if it is actually the production environment. If the test
environment is substantially different from the production environment the differences should be
explained here too.]
3.2 Network infrastructure
[Describe the network segments, routers, switches that will participate in the load test. Attach if
available the network topology diagram here]
3.3 Hardware resources
[Describe here the machines that are available for the load test and will participate in the load
test. Use the table below to fill out the machine names and their respective specifications.
Describe the machine’s name, its memory, processor, environment (i.e. Win 2000, win XP,
linux, etc), whether the machine has the application that needs to be tested installed (AUT =
Application under test), and the machine’s location (what floor, what facility, what room, etc)]
Machine
Memory
Processor
Environment
AUT
Location
Name
installed?
3.4 Summary of Hardware Resources:
[List here summary of all available resources, total available memory, and total number of
machines participating in the load test. Describe any servers and databases hosting the
application under test]
Example: 15 Win computer running on Win XP with 25 Gigs of available ram
MS SQL Server (version X) back-end for the application under test wit0h 2 win200
servers that have the following specs: RAM, CPU, etc
4.0 Testing Time Frame
[Describe the time frame for conducting the load test, and attach a Gantt chart with activities and
their expected duration. Also describe working hours for the load tests (i.e. first shift, third shift,
etc). A schedule for load testing activities should include time allocation for: the creation of test
scripts, planning the load test, re-executing the load tests if problems arise, pre-execution of the
load test scripts in proof of concept scenarios to validate that the test scripts can be executed with
a partial load of emulated end user, gathering collecting analyzing and interpreting of test results,
etc.]
5.0 Test Risks
SolovatSoft
Page 9 10/24/2004
Page 9 of 13
ADVERTISEMENT
0 votes
Related Articles
Related forms
Related Categories
Parent category: Business