Identify performance testing cycles and test case criteria
Before you deploy your new Pega Marketing application, establish a performance benchmark. This allows subsequent, iterative performance tests against the baseline to help identify any degradation in performance resulting from development efforts.
| Task ID | Task-070201 |
|---|---|
| Primary role | Test Manager - customer resource |
| Secondary role | Senior System Architect |
| Tertiary role | Deployment Architect |
Pega has very well described performance testing procedures; these are described here:
https://community.pega.com/knowledgebase/articles/performance/performance-0
To do a complete performance test, performance testing should cover the traditional tests of load, stress, soak, and scale. This is typically performed by the client’s team.
Why
Performance testing should prove that the system will operate at an acceptable level of performance in the live environment, when taking into account production volumes and loads.
How
The entry criteria for performance testing to start are:
- Test scripts exist to prove the SLAs
- A controlled test environment is available
- The application is loaded and test data is available
The exit criteria for testing to finish are:
- Test reports are available that describes the tests and results
This article describes a number of best practises for Performance Load testing.