Table of Contents

Page assertions


Only available versions of this content are shown in the dropdown

You can configure page assertions to determine if a page exists on the clipboard or if a page has errors.

You can configure page assertions on the following types of pages:

  • Embedded pages
  • Data pages
  • Data pages with parameters
  • Embedded pages within data pages that either have or do not have parameters
  • Top-level pages

For example, an activity runs every week to check the last login time of all operators and deletes any operator record (page) from the system if the last login was six months ago. When you test this activity:

  • Set up the clipboard to load an operator page that has the last login time as six months ago.
  • Create a page assertion that ensures that the page no longer exists after the activity runs.

  • Configuring page assertions

    Some rules, such as activities and data transforms, can create or remove pages from the system. You can create page assertions to determine whether or not a page exists after a unit test case runs. You can also assert if a property has an error and, if it does, what the message is so that you can validate that the message is correct.

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

Suggest Edit

Have a question? Get answers now.

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