Skip to main content

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

Unit test more rule types and configure activity status assertions (8.3)

Updated on May 3, 2021

Perform more comprehensive regression testing and verify application quality by unit testing more rule types and configuring activity status assertions. By unit testing more rule types and configuring activity status assertions, developers can more easily make sure the application meets requirements and functions as expected when they make changes.

Unit test more rule types

Unit test collection, declare expression, map value, and report definition rules and then convert the test runs into test cases. As with all automated unit tests for other rule types, Pega Platform compares test results to the expected results defined for the rule’s assertions (test conditions). If the test results do not meet the defined assertions, then the test fails.

"Unit testing map value rules"
Unit testing map value rules


"Create map value test case"
Creating a map value test case from a unit test run


Configure activity status assertions

Verify that an activity behaves as expected when it runs by configuring an activity status assertion that defines the status required for the activity to pass the test.

"Configuring activity status assertions"
Configuring activity status assertions


For more information about unit test cases, see Pega unit test cases.

For more information about configuring activity status assertions, see Configuring activity assertions.

  • Previous topic Track changes for branch merges in Deployment Manager (8.3)
  • Next topic Update and adapt existing scenario tests to UI changes (8.3)

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