Assertions

Use Pega unit test cases to compare the expected output of a rule to the actual results returned by running the rule. To define the expected output, you configure assertions (test conditions) on the test cases that the test, when run, compares to the results returned by the rule.

When a test runs, it applies assertions in the order that you define them on the Definition tab of the test case. All assertions, except for run time assertions, must pass for the test to be successful.

For example, an account executive wants to ensure that a 10% discount is applied to all VIP customers. You can create a test case that verifies that this discount is applied to all VIP customers in the database. If the test does not pass, the results indicate where the 10% discount is not applied.

See one of the following topics for more information:

• Configuring activity status assertions
• Configuring expected run-time assertions
• Configuring result count assertions
• Configuring property assertions
• Configuring list assertions
• Configuring page assertions
• Configuring decision result assertions
• Configuring assigned to assertions
• Configuring case status assertions
• Configuring attachment exists assertions
• Configuring case instance count assertions