Unit testing an activity

You can test an activity individually before testing it in the context of the application that you are developing. Additionally, you can convert the test run to a Pega unit test case.

You can use unit test the activity if one of the following criteria is met:

  • The Require Authentication to run check box is selected on the Security tab of the Activity form.
  • Your access role allows you to update rules that have the Applies To class of this activity.
  1. In the navigation panel of Dev Studio, click Records > Technical > Activity, and then select the activity that you want to open.
  2. Click Actions > Run.
  3. In the Run context pane, select the thread, test page, and data transform you want to use for the test.
    1. In the Thread list, select the thread in which you want to run the rule.
    2. In the Page list, select whether to copy parameter values from an existing page or to create an empty page:

      • To use parameter values from an existing clipboard page in the selected thread, click Copy existing page, and then select the page you want to copy.

      • To start from a page containing no parameter values, click Empty test page.

    3. Optional: To apply a data transform, select the Apply data transform check box, and then select the transform to apply.
      Note: The system always runs the rule instance on the RunRecordPrimaryPage, regardless of the page that you select from this list. If you convert this test run to a test case and the RunRecordPrimaryPage requires initial values, then configure the clipboard so that it populates the page with initial values. For more information, see Setting up your test environment.
  4. Optional: To change the values that are passed to the rule, provide the new values on the main test page.
  5. Click Run to run the test.
  6. To convert the test run into a Pega unit test case, click Convert to test, and then configure the test case. For more information, see Configuring Pega unit test cases.
  7. Optional: If the rule has errors, then click Trace to debug it using the Tracer tool. For more information, see Application debugging using the Tracer tool.