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.

Grouping scenario tests into suites

Updated on April 5, 2022

Group related scenario tests into test suites to run multiple scenario test cases in a specified order. You can then run the scenario test suites as part of purpose-specific tests, such as smoke tests, regression tests, or outcome-based tests. Additionally, you can disable or quarantine individual scenario tests for an application so that they are not executed when the test suite runs.

  • Creating scenario test suites

    To create a scenario test suite, add scenario test cases to the suite and then specify the order in which you want the tests 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.

  • Running scenario test suites

    Run scenario test suites to check application functionality. You can check the run history, add or remove test cases from the suite, or reorder the test cases before running the suite.

  • Viewing scenario test suite results

    After you run a scenario test suite, you can view the test 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