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

Updated on September 10, 2021

After you complete testing in a Test environment, it is common to perform User Acceptance Testing (UAT) in a designated UAT environment, which could be a pre-production environment. UAT ensures that users will be able to successfully complete work and meet business objectives.

Task IDTask-070301
Primary roleTest Manager - customer resource
Secondary roleSenior Decisioning Architect
Tertiary roleN/A

As your microjourney evolves, business users should be performing UAT. While end-to-end testing systematically tests the different paths through the microjourney™ flow, UAT tests specific business scenarios to ensure that the system behaves as the business expects. For example, a customer with a good credit score should receive higher loan offers than someone with a weaker credit score. UAT will focus on testing these types of business scenarios to see that the proper results are achieved.

For more information, see Execute user acceptance 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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us