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 regression testing cycles and test case criteria

Updated on September 10, 2021

Use regression tests to verify that application changes do not adversely affect existing product features.

Task IDTask-070401
Primary roleTest Manager - customer resource
Secondary roleSenior Decisioning Architect
Tertiary roleSenior System Architect

As you develop your application, add new components, or make changes to configuration, regression tests help ensure that existing features continue to work correctly. It involves re-running previously executed unit tests on unchanged parts of the application and verifying that the recent changes did not introduce any errors or unexpected behaviors.

Pega recommends an agile, iterative approach to application development, so regression tests should be a continous part of the build process. For more information, see Continuous Build and Test Sprints.

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