Skip to main content


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

Grouping test cases into suites

Updated on February 4, 2021

You can group related unit test cases or test suites into a test suite so that you can run multiple test cases and suites in a specified order. For example, you can run related test cases in a regression test suite when changes are made to application functionality.

  • Creating unit test cases for rules

    For most rules, you can create a reusable test case by converting a unit test to a test case, configuring case details, and then defining expected test results with assertions (test conditions). When the test case runs, the test results are compared to the expected results defined for the rule’s assertions. If the test results do not meet the defined assertions, then the test fails.

  • Opening a unit test suite

    You can view a list of the unit test suites that have been created for your application and select the one that you want to open.

  • Running a unit test suite

    You can run a unit test suite to validate rule functionality by comparing the expected value to the output produced by running the rule. Test cases are run in the order in which they appear in the suite.

  • Viewing unit test suite run results

    After you run a unit test suite, you can view the test run results. For example, you can view the expected and actual output for assertions that did not pass.

  • Adding cases to a test suite

    You can add test cases to a unit test suite. When you run a test suite, the test cases are run in the order in which they appear in the suite.

  • Viewing unit test suite run results

    After you run a unit test suite, you can view the test run results. For example, you can view the expected and actual output for assertions that did not pass.

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