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.

Unit testing a data page

Updated on April 5, 2022

Test a data page to ensure that you get the expected results by using the Run Rule feature before testing it in the context of the application that you are developing. Additionally, you can convert the test run into a Pega unit test case for reuse.

  1. In the navigation pane of Dev Studio,click RecordsDecision Decision Table, and then select the data page that you want to open.
  2. Click ActionsRun.
  3. From the Thread list in the Run context pane, select the thread in which you want to run the rule.
  4. In the main test page, enter values for parameters, if any, to pass to the rule.
  5. Select the Flush all instances of this data page before execution check box to delete any existing instances of the selected data page.
  6. Click Run.
  7. Optional: To convert the test into a unit test case for automated testing, click Convert to Test, and then configure the test case. For more information, see Creating unit test cases for rules.
  8. Optional: Click Show Clipboard to open the Clipboard and examine the pages that are generated by the unit test. For more information, see Clipboard pages created by the Run Rule feature.
  9. Optional: If the rule has errors, click Trace to debug the rule with the Tracer tool.
  • Data page testing

    Data page test cases are a way to validate that application data is loaded correctly. Data page test cases compare the expected value of one or more properties with their actual values in a data page.

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