Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Identify performance testing cycles and test case criteria

Updated on September 10, 2021

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 IDTask-070201
Primary roleTest Manager - customer resource
Secondary roleSenior System Architect
Tertiary roleDeployment Architect

Pega has very well described performance testing procedures; these are described here: 


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.


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.


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.




Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us