Including assertions in your journey

When you define a journey using the mabl trainer, you can include assertions that describe logic that mabl should use to confirm that your application is in a correct state at a specified step in a test run.

Important Assertion Information

All find actions in mabl, including assertions, will automatically wait up to 30 seconds for the targeted element to appear. There is generally no need to add an additional wait step before an assertion, unless the element will take more than 30 seconds to appear in your app or if the element comes into existence without being fully realized. In the latter case, a wait step before the assertion may be necessary as mabl will evaluate as soon as it detects that the target element exists. Find more information about wait steps in mabl at our "Adding wait steps with the mabl trainer" doc.

Currently, mabl supports the following assertion types:

  • Selected element is present
  • The inner text of the selected element:
    • Equals
    • Does not equal
    • Contains
    • Does not contain
    • Starts with
    • Does not start with
    • Greater than
    • Less than
    • Greater than or equals
    • Less than or equals

Step-by-step instructions for adding an assertion

  1. In the mabl trainer window, click "Add assertion."
Where to find the "Add assertion" link within the mabl Trainer.

Where to find the "Add assertion" link within the mabl Trainer.

  1. Click on the element that you want to include in your assertion.
  1. Choose your assertion type from the drop-down.
Scroll through the list of the types of assertions you can make about a web element

Scroll through the list of the types of assertions you can make about a web element

  1. Complete the additional assertion fields, if applicable.
  2. Click "Apply Assertion."
  3. Continue with your training session, if applicable.
A sample of how to alter and apply an assertion.

A sample of how to alter and apply an assertion.