Skip to main content

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.

Grouping test cases into suites

Suggest edit Updated on April 5, 2022

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 suites

    To create a unit test suite, add test cases and test suites to the suite and then modify the order in which you want them to run. You can also modify the context in which to save the scenario test suite, such as the development branch or the ruleset.

  • Creating unit test suites with AUT

    Unit Test Suites identify a collection of Test Cases and their rulesets, and a user (Operator ID) whose credentials are used to run the Unit Test Suite. Unit Test Suites are used to automatically run groups of test cases together and make unit testing more efficient.

  • 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.

Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

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