You are here: Project delivery > Tools - Project delivery > Automated Unit Testing (AUT) landing page

Landing PagesApplication category — Automated Unit Testing page
Automated Unit Tests, Dashboard, Reports, and Schedule tabs

Designer StudioAccess

Category

Page

Application

Automated Unit Testing

When your operator ID has the AutomatedTesting privilege through an access role, you can use the Automated Unit Testing landing page to work with recorded test cases and unit test suites, including playing them back, scheduling when to run them, and examining their results. The Automated Unit Testing landing page contains the Automated Unit Tests, Dashboard, Reports, and Schedule tabs.

Using the Automated Unit Tests tab

Use this tab to work with and view information about the current application's recorded test cases and saved unit test suites. From this tab, you can:

This tab lists the unit test suites and test cases that are stored in:

See Application form — Completing the General tab.

For example, if your test cases are stored in Tests:01-01 and that RuleSet is in the current application's Application RuleSets array, those test cases are listed on this tab.

Field

Description

Show Select one of these choices:
  • Unit Test Cases, to work with the application's test cases and view information about them.
  • Unit Test Suites, to view information about the unit test suites and see which test cases are associated with which unit test suites.

Viewing, playing back, and re-recording test cases

If you choose Unit Test Cases in the Show field, a list of saved test cases appears. To see any resume test cases associated with a flow test case, drill down through the folder structure of the parent flow test case. In the list, you can examine information about the test case, such as when it was created and the status of its last run. If results are saved for a test case, you can click its link in the Saved Results column to view them.

To play back a test case, click its name in the Name column. The Run Rule (for non-flow test cases) or Testing Flow (for flow test cases) window opens and you can play back that test case.

Re-record menu optionTo re-record a test case, right-click the test case name and select Re-record from the context menu. The Run Rule (for non-flow test cases) or the flow window opens for the rule associated with that test case. Proceed with running the rule and then click the Save Test Case button to replace the previous recording with the new one. Note: 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 Test Case and Unit Test Suites and withdrawing test cases and suites

Context menu optionsTo open the rule for either a test case or suite, right-click its name and select Open from the context menu.

To withdraw a test case or suite, right-click its name and select Withdraw from the context menu. Withdrawn test cases and suites are not displayed on the Automated Unit Tests tab. (See Withdrawn rule.)

Using the Dashboard tab

Use this tab to see the results of your recent unit test suite runs.

The ten most recent runs are displayed. For results from earlier runs, use the Reports tab.

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

To examine the results from a run of a particular unit test suite:

Click the corresponding item in either the graph or in the report below the chart. The list of test cases in that unit test suite run is displayed with details about their individual runs.

To examine the results from a specific test case run, click that test case in the list.

From the differences found display, you can select to have differences ignored in future runs of the test case:

  1. Select specific differences to have the system ignore them either for that individual test case, or for all test cases in the application.
  2. Click Save Ignores to save your choices.

For activity test cases, if the activity test case has a white list, then differences are reported only if they are differences for pages and properties on the white list. If the test case has a white list and the only differences are for pages and properties not on the white list, then those differences are not reported. If differences are found for white-listed items, you can select to remove the item from the white list for that test case.

Using the Reports tab

Use this tab to see the test results from executing specific unit test suites. When you select a particular unit test suite from the drop-down list, a chart of the results from each time it ran appears along with an indication of how the results compare to the expected results. For a given unit test suite, the display shows results from the last fifty (50) runs of that unit test suite.

To examine the results from a specific run:

Click the appropriate line from the report that appears below the chart, or click the entry within the chart itself. The list of test cases in that unit test suite run is displayed with details about their individual runs.

To examine the results from a specific test case run, click that test case in the list.

From the differences found display, you can select to have differences ignored in future runs of the test case:

  1. Select specific differences to have the system ignore them either for that individual test case, or for all test cases in the application.
  2. Click Save Ignores to save your choices.

For activity test cases, if the activity test case has a white list, then differences are reported only if they are differences for pages and properties on the white list. If the test case has a white list and the only differences are for pages and properties not on the white list, then those differences are not reported. If differences are found for white-listed items, you can select to remove the item from the white list for that test case.

Using the Schedule tab

Use this tab to:

To create a unit test suite:

  1. Click Create Suite. The New Rule window opens.
  2. Enter the requested information for creating a new unit test suite. (See also Unit Test Suite form — Completing the Contents tab.)

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

  1. Locate the suite you want to run in the list and then click the calendar button (Calendar) in its Schedule column. The Schedule Unit Test Suite window opens.
  2. In the Pattern section, specify how to run this unit test suite. When the run is complete, the system displays the results in the Dashboard tab.
Pattern  

To run immediately:

Select Run Now and click OK.

The system runs the unit test suite in the foreground.

The Run Now choice is typically used when you want to try out a unit test suite using your RuleSet stack. For example, if you have rules checked out and you want to regression test against a unit test suite before checking the rules back in, use the Run Now option.

Because the unit test suite runs in the foreground, if the unit test suite contains many test cases, using Run Now might take a few minutes to complete.

To run this unit test suite only once:

  1. Select One Time.
  2. In the Start field, specify the starting time for this run. You can type in a date-time (for example 8/31/2010 09:42 PM) or click the calendar button (Calendar) to open the Calendar window to select the date and time.

At the starting time, the system runs the unit test suite in the background.

The One Time choice is typically used to try out the unit test suite and verify that the returned results are what you expect to get; for example, to test out the completion email notification. You might want to use this choice instead of Run Now when the unit test suite contains many test cases and might take a long time to complete.

To run this unit test suite on a recurring basis:

  1. Select one of the standard recurrent time periods: Daily, Weekly, Monthly, or Yearly.
  2. In the Start field, specify the starting time for the first run of the recurrent pattern. You can type in a date-time (for example 8/31/2010 09:42 PM) or click the calendar button (Calendar) to open the Calendar window to select the date and time.
  3. Specify the appropriate recurrence settings for the run pattern. For example, if the pattern is Weekly, select the day of the week.

At the starting time, the system runs the unit test suite in the background. From that point onwards, the system runs the unit test suite according to the chosen recurrent pattern.

This choice is used when you are satisfied with the behavior of the unit test suite and want to schedule it for standard testing operations.

Using the Calendar window:

In the Calendar window, select a time and month using the drop-down lists, and then click the numerical day in the calendar grid. (Note: Even if the intended day is already highlighted, you must click the day to save the date-time selection.) When you click the day, the Calendar window closes and the selected date is displayed in the Start field.

For scheduled runs (runs other than the Run Now choice):

  1. Optional: Select to run the unit test suite 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 using the RuleSets and access rights associated with that operator. If the operator ID form has multiple access groups, their default one is used.
  2. Optional: Send the completion email to multiple email addresses. Use the Send Completion Email to array to specify the email addresses.

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

  3. Click OK to save the schedule. The Schedule Unit Test Suite window closes. The unit test suite run is added to the list of currently scheduled unit test suites on the Schedule tab.

By default, the Pega-AutoTest agents which run scheduled unit test suites run every five minutes. (Scheduled unit test suites are those where Run Now is not selected.) When a scheduled unit test suite is due to run, the agent activity runs that unit test suite. When the suite is finished, the agent activity sends the completion email message 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 array, no email message is sent.

Definitions application, landing page
Related topics About Automated Unit Testing

UpTools — Application
Help System home pageHelp Home