Skip to main content


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

Scenario testing on Pega Platform

Updated on December 13, 2021

Run scenario tests against a user interface to verify that the end-to-end scenarios are functioning correctly. You can record a set of interactions for a case type or portal in your scenario tests. You can also group related scenario tests into test suites to run multiple scenario test cases in a specified order.

In versions of Pega Platform earlier than 8.5, scenario testing is provided as a native Pega Platform and is released as an independent component.

  • Application: Scenario testing landing page

    The scenario testing landing page provides a graphical test creation tool that you can use to increase test coverage without writing complex code.

  • Creating scenario tests

    Record a set of interactions for a case type or portal in scenario tests. You can run these tests to verify and improve the quality of your application.

  • Opening a scenario test case

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

  • Editing scenario tests

    Ensure that the test covers your current portal or case type scenario by updating an existing scenario test when the user interface or process flow changes. You can save time and effort by keeping existing tests functional instead of creating new ones.

  • Grouping scenario tests into suites

    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.

  • Viewing scenario test results

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

  • Other features

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