Close popover

Table of Contents

Working with the deprecated AUT tool

Version:

In older versions of Pega Platform, automated unit tests were created using the Automated Unit Testing (AUT) tool, which has since been replaced by PegaUnit testing. If you have automated unit tests that were created using AUT and they haven't been changed to PegaUnit test cases, then you can switch back to AUT to manage those tests.

AUT has been deprecated and is not supported in the current version of Pega Platform. Switch to and use AUT only if you have existing automated unit tests created with AUT. See PegaUnit testing more information.

Note the following behavior:

  • To use AUT, your operator ID must have the AutomatedTesting privilege through an access role.

  • Switch from PegaUnit testing to AUT by clicking Configure Automated Testing Test Cases and clicking Switch to old version on the Automated Unit Testing landing page.

  • Click the Test cases tab of the Automated Unit Testing landing page to display options for creating unit tests for activities, decision tables, and decision trees.

  • If you are using the Automated Unit Testing landing page and then log out of the system, you can click Configure Application Automated Unit Testing , and then click Switch to new version to restore the Automated Testing landing page.

Viewing, playing back, and rerecording test cases

  1. Click the Automated Unit Tests tab.
  2. Select Unit Test Cases in the Show field.
    • To play back a test case, click its name in the Name column.
    • To rerecord a test case, right-click the test case name and click Re-record.
      If the underlying test case rule belongs to a ruleset that uses the check-out feature, you must have the test case rule checked out to you before re-recording the test case.

Opening rules in test cases and unit test suites

  1. Click the Automated Unit Tests tab.
  2. Right-click a test case or suite and click Open to open its rule.

Withdrawing test cases and unit test suites

  1. Click the Automated Unit Tests tab.
  2. Right-click a test case or suite and click Withdraw.

Withdrawn test cases and suites are not displayed on the Automated Unit Tests tab.

Unit test suite run results

You can view the results of your recent unit test suite runs in either the Dashboard tab or Reports tab. The Dashboard tab displays the ten most recent runs. The Reports tab displays earlier results and, for a given unit test suite, shows results from the last fifty (50) runs of that unit test suite.

If you ran a unit test against a saved test case for a decision table, decision tree, activity, or Service SOAP rule and selected the All Cases option in the Run Rule form, those results also appear in the Dashboard tab.

For activity test cases, if the activity test case has an approval list, differences are reported only for pages and properties on the list. If the test case has an approval list and the only differences are for pages and properties not on the list, those differences are not reported. If differences are found for items on the approval list, you can remove the item from the approval list for that test case.

Creating and scheduling unit test suites

To create a unit test suite:

  1. Click the Schedule tab.
  2. Click Create Suite.
  3. In the New Rule form, enter the requested information for creating a unit test suite.

To run a unit test suite or to schedule a run:

  1. Click the Schedule tab.
  2. Click the Calendar icon in the Schedule column for the unit test suite you want to run.
  3. In the Pattern section in the Schedule Unit Test Suite window, specify how to run this unit test suite. When the run is complete, the system displays the results in the Dashboard tab. When you select To run immediately, the system runs the test suite in the foreground; for all other options, the system runs the test in the background.
  4. For scheduled runs, you can specify additional options.
    1. Select to run the unit test suite by using a different operator ID. In the Advanced Settings section, enter the Operator ID in the Override Default and Run Suite As field. The system runs the unit test suite by using the rulesets and access rights associated with that operator. If the operator ID form has multiple access groups, the default access group is used.
    2. Send the completion email to multiple email addresses. Use the Send Completion Email to field to specify the email addresses.

      If you do not want any emails sent, clear the Send Completion Email field.

  5. Click OK.
By default, the Pega-AutoTest agents run scheduled unit test suites run every five minutes. When the suite is finished, the agent activity sends an email with the results. By default, this email is sent to the operator who requested the unit test suite run and to any email addresses listed in the Send Completion Email array. If no email addresses appear in that field, no email message is sent.

  • Creating test cases with AUT

    You can automate testing of rules by creating test cases for automated unit testing. Automated unit testing validates application data by comparing expected output to the actual output that is returned by running rules.

  • Creating unit test suites with AUT

    Unit Test Suites identify a collection of Test Cases and their rulesets, and a user (Operator ID) whose credentials are used to run the Unit Test Suite. Unit Test Suites are used to automatically run groups of test cases together and make unit testing more efficient.

  • AUT test suite – Create or Save as form

    Unit Test Suites – Completing the Create or Save As form

  • AUT test suite – Contents form

    Use the Contents tab to define the unit test suite. Specify a user (Operator ID) that the Pega-AutoTest agents are to use by default when running the suite, and select the test cases to include.

  • Viewing test details and results on the Application:Unit testing landing page

    On the Application: Unit testing landing page you can run unit test cases and test suites that are not marked as disabled, and view reports to check the quality of your application to identify rules that did not pass unit testing.

Suggest Edit

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.