Load And Performance Test Plan Page 13
ADVERTISEMENT
1
2
3
4
5
6
7
8
9
10
11
12
13Project Name Test Plan
Load test strategy has been peer reviewed, accepted
and signed off.
Test lab and PCs are available and have been
scheduled for the tests
End users, customer, and project members have been
notified in advance of the execution dates and hours
for the load test
Test scripts have appropriate naming conventions
and have been saved in a shared and backed-up
repository or test management tool
Test environment has been frozen without the
introduction of new changes for both the creation of
test scripts and the execution of the load test.
Hardware equipment has sufficient RAM to emulate
the total expected number of production end users.
Throughput emulation has been properly designed to
have the number of emulated end users = to the total
number of expected production users.
Estimates of kilobytes of data sent per user across
the LAN/WAN have been identified
Application under test is stable and has been
previously tested for functionality and contains the
latest patches.
The execution schedule allows for the completion of
all the load tests with 3 weeks left before the
deployment deadline.
All service level agreements, response time
requirements have been covered with test cases.
The load test strategy includes the testing of the
application under test at the GUI level to include
response times from the client side of the
application.
An SME or functional expert has signed off the
automated test script
All recommendations and suggestions have been
presented to the project’s decision makers.
Test scripts have been properly sequenced
Confidence levels that will be used for the test
results have been identified
A shared repository exists to save all test results
SolovatSoft
Page 14 of 13
ADVERTISEMENT
0 votes
Related Articles
Related forms
Related Categories
Parent category: Business