Including assertions in your test

When you define a test 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.

Currently, mabl supports the following assertion types:

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

Step-by-step instructions for adding an assertion

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.

  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. You can select a custom attribute of an element as well as any other attribute for the element
  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.

Cropping assertion screenshots to individual elements

mabl supports cropping the captured screenshot to the element instead of full screen when creating an assertion in the Trainer. This is useful if you just want to make it easier to see which element mabl interacted asserted on in detail, or if you'd like to do visual comparisons on the asserted element, even if the element moves around the screen.

The option is available on any assertion when training a test. To take advantage of it just create a new assertion, or edit an existing one and check the box like below.

Current Scrolling Limitation

mabl assertion steps do not currently auto-scroll to elements off screen. Thus, consider adding a javascript step to scroll to the element before the assertion if you want to capture an element that may not be in the current viewport.

You can find an example JavaScript snippet here in our GitHub repository.


Including assertions in your test


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.