Page History

Risk

Contingency

Production-like test environment not available

Utilize development or production environment. Results may not be indicative of production and therefore cannot be used as a benchmark. Production performance issues may not be identified during testing.

Production-like setup and settings not available.

Use the closest setup and settings we can. Results may not be indicative of production and therefore cannot be used as a benchmark. Production performance issues may not be identified during testing.

Fully operational test tools not available.

Wait until the test tools are available or find and use another test tool(s). This will extend the time required to perform testing.

Test time increases due to changes in scope requiring additional test analysis and/or test case creation

If test time cannot be increased, reduce/cut performance testing scenarios and execute highest priority scenarios initially followed by lower priority tests until test time runs out

Involvement of subject matter experts (SMEs) for all stages of the testing effort not sufficient.

If test time cannot be increased, reduce/cut performance testing scenarios and execute highest priority scenarios initially followed by lower priority tests until test time runs out

Inadequate Non-functional Requirements

Missing pass/fail criteria invalidates benchmarking. Missing load modeling invalidates all scenarios. Perform only a brute stress test to try and flush out major bottlenecks and functionality under load issues. Additionally an endurance test can be run to attempt to identify memory leaks. All tests will be less indicative of real world usage scenarios.

Insufficient access to systems in order monitor (This includes any necessary server side scripts which may need to be developed in order to capture desired metrics.)

Root cause analysis will be difficult is possible. Testing time will most likely need to be extended and scenarios may be abbreviated due to time constraints.

Substantial issue(s) which requires significant modifications to the application or re-configuration of the system are encountered.

Some testing may need to be re-done, possibly including re-scripting etc. This would extend testing time.

Excessive number of bottlenecks encountered and/or issue correction time.

Extend testing time.

Test time increases due to changes in scope requiring additional test analysis and/or test script/scenario creation

If test time cannot be increased, reevaluate priorities and risk and test according to new priorities.

Conflicting information provided.

Project manager will work to resolve any conflicting information, goals, and/or instructions received.

Key Deliverables

Description

Expected Delivery Date

Resource

Performance Test Plan

This document.

After all non-functional requirements and other needed data is delivered

Questcon

Performance Test Scripts

Automated scripts used to deliver load.

30 business days after test plan finalization and environmental needs are met.
(2.5 days for each script)

Questcon

Performance Test Scenarios

Automated execution designs used to conduct performance tests.

5 business days after scripts are developed.
(~.75 days for each scenario)

Questcon

Execute Performance Tests

Running of scenarios.

10 business days
(~1 day for 7 scenarios and 3 days for endurance scenario)

Questcon

Status Reports

Accomplishments, issues and plans.

Weekly

Questcon

Defect Reports

Entered in Jira as they are discovered.

Ongoing during test execution

Questcon

Performance Test Summary Report

Details the results of the testing effort.

3 business days after the last performance test is completed.

Questcon

Milestone

Target Timeframe

Summation of Activities

Develop performance test plan

01/15/2008 - 02/05/2008
15 Business Days Days

• Analyze existing design documents, notes, and other available materials
• Develop test plan document

Review performance test plan

02/05/2008 - 02/11/2008
3 Business 3 Business Days

• Review, clarify, correct, and update the test plan
• Client approval of test plan

Build Performance test scripts

//2008 - //2008
30 Business Days

• Author test scripts in automated tool

Build Performance test scenarios

//2008 - //2008
5 Business Days

• Setup web server and database server
• Load application under test
• Setup logins and authorizations

Setup test data

//2008 - //2008
1 Business Day

• Review & analyze test cases to target data to load in test environment
• Load initial test data set

Execute performance tests

//2008 - //2008
10 Business Days

• Execute documented performance test scenarios
• Communicate with the development team when issues are found
• Maintain a test run log
• Track test metrics

Create test summary

//2008 - //2008
3 Business Days

• Create and deliver a test summary report to include:
  • Summation of planned/actual test activities
  • Deviation from planned activities
  • Summary of defects (open defects)
  • Summary of test metrics

TOTAL:

73 Business Days