1

Understand the Objective of the Test

• The objective of the test must be clearly identified. For example, there should be no significant difference in product response time for users with different internet connection speeds.
• The outcome of the test must be clearly documented and expressed as a range of values.

2

Specify the Test Configuration

• Identify the test configuration.
• Document any test result deviations that depend on the test configuration. For example, a typical user configuration as opposed to a simulated lab configuration.
• Document external conditions that might affect the test timing.

3

Design the Test

• Map out the test conditions including prerequisites and the scenario being timed. Review the scenario to determine areas where performance is critical and where it is not. Work with the architects to understand the performance model used to instrument the code.

4

Document the Test Steps

• Itemize the test steps so all testers who execute the performance tests perform each step the same way. Failure to itemize the test steps can result in incorrect measurement of performance. Use automation to build test cases wherever possible.
• Add the automated test cases to the test folder for the quality of service requirement and the iteration tests. Check in the tests and update the test approach worksheet with any test data or other considerations for the test.

The performance tests are completed and checked in.

The performance tests verify that quality of service requirements pertaining to performance are met.