Working with the deprecated AUT tool
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.
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 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 , and then click Switch to new version to restore the Automated Testing landing page.
Viewing, playing back, and rerecording test cases
- Click the Automated Unit Tests tab.
- 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.
Opening rules in test cases and unit test suites
- Click the Automated Unit Tests tab.
- Right-click a test case or suite and click Open to open its rule.
Withdrawing test cases and unit test suites
- Click the Automated Unit Tests tab.
- 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:
- Click the Schedule tab.
- Click Create Suite.
- 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:
- Click the Schedule tab.
- Click the Calendar icon in the Schedule column for the unit test suite you want to run.
- 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.
- For scheduled runs, you can specify additional options.
- 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.
- 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.
- Click OK.
- Create or Save as form in AUT test suite
Unit Test Suites – Completing the Create or Save As form
- Creating unit test suites
To create a unit test suite, add test cases and test suites to the suite and then modify the order in which you want them to run. You can also modify the context in which to save the scenario test suite, such as the development branch or the ruleset.
Previous topic Understanding Pega Platform 7.2.2 and later behavior when switching between Pega unit testing and Automated Unit Testing features Next topic Creating test cases with AUT