These Performance Testing Initiation Best Practices allow teams to identify if they have correctly designed their performance tests before test execution
Stakeholder Alignment
| Business Stakeholders Identified |
High |
|
| IT Stakeholders Identified |
High |
|
| Performance Test Architect Identified |
High |
|
| Performance Test Engineer Identified |
Medium |
|
| Dedicated Performance Test Environment Identified |
High |
|
Non-Functional Requirements
| Average Transactions per day for each key flow |
High |
|
| Average Transactions per user for each key flow |
High |
|
| Peak Transactions during peak hour/minute for each key flow |
High |
|
| Data Generated in each table identified for 18+ months past go live |
High |
|
| Determine the need for a Performance Test, Load Test, Stress Test or Endurance Test based on the above requirements. |
High |
|
Acceptance Criteria
| Targets for 90 percentile Response Time Identified |
High |
|
| Targets for transaction throughput identified for each respective test (Performance, Load, Stress and Endurance) based on estimated volumes. |
High |
|
Test Design
| Test design incorporates realistic usage scenarios including “think time”. |
High |
|
| Test design incorporates variability and realistic test data |
High |
|
