Table of Contents

Configuring activity status assertions


Only available versions of this content are shown in the dropdown

You can verify that an activity returns the correct status when it runs by configuring an activity status assertion. You can also assert if an activity has an error and, if it does, what the message is so that you can validate that the message is correct.

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. In the Assertion type list, click Activity status.

  3. In the Value list, click the status that you expect the activity to return when the test runs.

  4. To validate the message that displays for the activity, select Validate message, select a Comparator, and then enter the message that you want to validate in the Value box.

  5. Optional:

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

  6. 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 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.

Suggest Edit

0% found this useful

Have a question? Get answers now.

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