Table of Contents

Configuring assigned to assertions


Only available versions of this content are shown in the dropdown

For flows and case types, you can use the assigned to assertion to verify that an assignment is routed to the appropriate work queue or operator.

If you have multiple assignments on a flow or test case, you can route each assignment to an operator ID or work queue. Clipboard pages are created for each assignment under the pyWorkPage page and capture the assignment details, including the operator ID or work queue to which the assignment was routed. The assigned to assertion compares the operator ID or work queue to the last assignment that is configured on the flow or case type, which depends on where you stop recording the flow or case type.

For example, your flow has a Customer Details assignment, which is routed to the operator ID johnsmith. It also has a subprocess with an Account Information assignment, which is routed to the account_processing work queue.

If you record only the Customer Details assignment, the assigned to value is johnsmith. If you also record the Account Information assignment, the assigned to value is account_processing.

Open the unit test case. For more information, see Opening a unit test case.

  1. On the bottom of the Definition tab, click Add expected result.

  2. From the Assertion type list, select Assigned to.

  3. From the Assigned to list, select Operator or Work queue.

  4. Select a comparator from the Comparator list.

  5. In the Value field, press the Down Arrow key and select the operator ID or work queue.

  6. Optional:

    To add a comment, click the Add comment icon, enter a comment, and click OK.

  7. Click Save.

  • Defining expected test results with assertions

    Use unit test cases to compare the expected output of a rule to the actual results returned by running the rule. To define the expected output, you configure assertions (test conditions) on the test cases that the test, when run, compares to the results returned by the rule.

  • Converting unit tests to test cases
  • Creating unit test cases for rules

    For most rules, you can create a reusable test case by converting a unit test to a test case, configuring case details, and then defining expected test results with assertions (test conditions). When the test case runs, the test results are compared to the expected results defined for the rule’s assertions. If the test results do not meet the defined assertions, then the test fails.

Suggest Edit

Have a question? Get answers now.

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