Skip to main content

Embedding and reusing scenario tests

Suggest edit
Updated on December 13, 2021

You can record a scenario test and save it as a reusable component to embed in one or more scenario tests. Reusing scenario tests reduces the effort to create the same scenario test multiple times.

When you run a scenario test with embedded scenario tests, the system runs the embedded scenario tests in the sequence in which the tests are listed. Then, the system runs any other setup steps.

Note the following information about reusing scenario tests:

  • The scenario tests that you want to embed has to belong to the same user portal.
  • There is no limit on the number of reusable scenario tests that you can embed in a scenario test.
  1. Record and save the scenario test that you want to configure as a reusable test. For more information about recording scenario tests, see Creating scenario tests.
  2. In Dev Studio, open the test case. For more information, see Opening a scenario test case.
  3. On the Definition tab, at the top of the Scenario test case page, select the Reusable check box.
    Note: If a scenario test is configured to use embedded scenario tests, you cannot mark that scenario test as reusable.
  4. Click Save.
  5. Open the scenario test into which you want to embed the reusable scenario test.
  6. Click the Setup & Cleanup tab.
  7. Expand Embed and execute other test cases on start.
  8. Click Add scenario test case.
  9. In the Of class field, press the Down arrow key, and then select the class to which the scenario test case belongs.
  10. In the Name of test case field, press the Down arrow key, and then select the test case that you want to reuse.
  11. Click Save.
What to do next:

Review the video.

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