Summary

Part of the Automated Testing facility, test suite rules identify an access group and a collection of test cases and their RuleSets. When you run individual test cases from the Run Rule window, the test case runs in your session as part of your requestor.

Test suites, however, run in the background as part of the Pega-ProCom agent. When the agent runs the test suite, it uses the access group specified in the test suite rather than the access group specified for the batch requestor type data instance or for the agent queue.

You can create a test suite that includes all the test cases for a specific rule type or you can select individual rules and specify the sequence in which to run them.

Suggested Approach

Before you begin creating test suite rules, complete the following tasks:

• Determine which access group to assign to the test suite. Access groups must give the agent access to the test suite rule and the test cases listed in the test suite. If you need to create a new access group, do so now.
• You can create a test suite that contains all the test cases for a specific rule type and then constrain that list with a When rule. The test cases for the rules identified by the When rule are included in the test suite. Determine whether you need to use a When rule in your test suite and, if so, create it now.

Creating Test Suites

To create a test suite:

1. From the Rules by Type explorer, select SysAdmin > Test Suite.
2. From the list, click the New toolbar icon.

3. In the New Test Suite form, name the test suite. Specify the test case RuleSet and version that you created for your test cases. Click Create.

4. On the Contents tab, specify the RuleSets that hold the test cases you want to include in the unit test suite. The default RuleSet for this field is the RuleSet chosen when you created the unit test suite.
5. Enter the user ID the agent uses when running this unit test suite. The user ID gives the agent access to the RuleSet that the unit test suite belongs to as well as the RuleSets listed in the RuleSets field. This field defaults to the Operator ID that created the unit test suite.
6. In version 5.5, you can choose to not delete the work object created by the test suite by checking the Remove Test Work Objects? check box. This box is checked by default.
7. Select the test cases you want to include in this unit test suite in one of the following ways:

   If the order in which test cases run is significant, do not include entries in the Rule Types section.

   • Specify test cases by application name and version.
   • Specify test cases by rule type.
     • Specify a When rule to further constrain the list of test cases. In this case, the test cases for the rules identified by the When rule are included in the unit test suite. This option is useful when the order in which the test cases run is not significant.
   • Search for and then select individual test cases. Enter the name or partial name in the Test Case Name field and click Query. Select the rules you want from the subsequent list. If the order in which the test cases run matters, be sure to list them in the order in which they are to run.

If you configure selections in both the Rule Types section and the Query Test Cases section, note that the test cases defined in the Rule Types section run before the test cases listed in the Query Test Cases section.

8. If you specified individual test cases, their RuleSets appear in the list next to their names. Verify that these RuleSets are included in the RuleSets for Test Cases list at the top of the form. If a RuleSet is not in the list, add it now. Otherwise, the test case rule will not run when the unit test suite runs.

9. On the History tab, enter a description in the Full Description and Usage fields.
10. Save the test suite rule.