Modifying PegaUnit test cases in the Edit Test Case rule form

In the Edit Test Case rule form, you can run the test case and view its results. You can also modify and configure settings.

Note: The Edit Test Case rule form appears after you click Create and open or Create and close or save the test case. Otherwise, the Create Test Case rule form appears. Some options differ between the rule forms. See Configuring PegaUnit test cases in the Create Test Case rule form for more information.

Complete any of the following actions:

• Run a test case by clicking Actions > Run. You can run a test after you save the rule form.

• Click View details in the banner to view more details about the latest result. This button appears after a test case has been run. See PegaUnit test case run results for more information.

• Click View previous runs in the banner to open a new dialog box that displays the test date, the run time, expected run time, and whether the test passed or failed. Click the row of a test case to view detailed test results. This link appears after a test case has been run.

• Modify the parameters, if any, that are sent to the test by clicking the Gear icon next to the parameters that were sent.

  There are two parameters for strategy rules:

  • componentName: Name of the component (for example, Switch) that you are testing.
  • pzRandomSeed: Internal parameter, which is the random seed for the Split and Champion Challenger components. It is generated for all components but applies only to the Split and Champion Challenger components.

  ​If you rename either the componentName or pzRandomSeed parameter, the test case does not return the results that you expect to see.

  For example:

  • If you configure the test to run on a different component, the test might fail if a property is not found.
  • If you change the pzRandomSeed value on Split or Champion Challenger shapes, the test fails.

• For flow rules and case types, view the path of the flow or case type. The path does not display:

  • Child cases that do not have flow actions configured on them.

  • Flow actions on which post-processing is not performed.

• Modify the description of the test case.

• Configure assertions (test conditions) to compare the expected output of the test with the actual test results. See Assertions for more information.

• Apply one or more data pages, data transforms, or activities to set up the clipboard before running a test in the Setup & Cleanup tab. You can also use activities to create any required test data, such as work or data objects. See Setting up your test environment for more information.

Note: The Setup & Cleanup tab appears for strategy rules only when you create test cases for them in Designer Studio.

• Apply additional data transforms or activities to clean up the clipboard in the Setup & Cleanup tab. See Cleaning up your test environment for more information.

Open topic with navigation