1.        Reference Documents

Reference information used for the development of this plan including:

·          Business requirements

·          Technical requirements

·          Test requirements

·          …and other dependencies

1.     Scope

What does this document entail?

What is being tested?

What is the overall objective of this plan? For examples:

·          To document test objectives, test requirements, test designs, test procedures, and other project management information

·          To solicit feedback and build consensus

·          To define development and testing deliverables

·          To secure commitment and resources for the test effort

2.     Approach   

The high-level description of the testing approach that enables us to cost effectively meet the expectation stated in the Scope section.

3.     Load Test Types and Schedules         

Specify the test types (with definition for each) to run:

·          Acceptance test

·          Baseline test

·          2B1 load test

·          Goal-reaching test

·          Spike test

·          Burstiness test

·          Stress test

·          Scalability test

·          Regression test

·          Benchmark test

 

Be specific:

·          Specify what tests you will run

·          Estimate how many cycles of each test you will run

·          Schedule your tests ahead of time

·          Specify by what criteria you will consider the SUT to be ready-for-test

·          Forward thinking: Determine and communicate the planned tests and how the tests are scheduled

4.     Performance/Capability Goals

Identify goals:

·          Percentage of requested static pages that must meet the acceptable response time?

·          Percentage of requested scripts that must meet the acceptable response time?

·          The baseline multiplier (2x, 4x, ...) that the system must be capable of handling?

·          The spike ratio that the system must be capable of handling?

·          The peak ratio that the system must be capable of handling?

·          The burstiness ratio that the system must be capable of handling?

·          Tolerance ratio: Imposed load ? 25 %?

·          Safety ratio: Imposed load x 2?

·          Spike ratio: Imposed load x 3?

·          Burstiness ratio: Imposed load x 5?

·          Increase the load by multiplying the load baseline by 1x, 2x, 3x, 4x, Nx gradually until unacceptable response time is reached.

Other questions to consider:

·          What is response time?

·          What is acceptable response time?

·          Which metrics should we collect?

·          What is the correlation between demand and increased load?

·          How do we determine which components are problematic?

·          How do we correlate financial implications?

5.     Load Testing Process, Status Reporting, Final Report

Describe the testing and reporting procedures. For example:

·          The internal test team will execute all created scripts.  These Scripts will be generated and executed against the system at least three times.  We will execute these scripts again, after subsequent hardware, software, or other fixes are introduced. 

 

·          Test team will baseline load as follows:

·          Load Test Team will test Nile.com with 1000 Simultaneous Clients/Users, and report back on the following metrics:

·          Response Time each transaction hitting the Web site.

·          Any web or database server errors as reported in the data log.

·          Round time

·          Failed Web Transactions

·          There will be Status Reports sent to Team Lead detailing:

·          Performance tests run

·          Performance metrics collected

·          Performance Errors and status

·          Number of Bugs Entered

·          Status Summary

·          Additional load testing, if needed.

·          The Final Report will include summary bug counts, overall performance assessment, and test project summary items.

Additional Information to be provided by Development Team:

1.        Build Schedule

2.        Acceptance test criteria

3.        Deployment Plans

6.     Bug Reporting and Regression Instructions

Describe the bug reporting process and the fix/change regression test procedures.

7.     Tools Used

State the tool solutions for the project:

·          Load testing tools

·          Monitoring tools

Tool Options:

·          Product vs. Application Service Provider (ASP)

·          Freeware

·          Lease or rent