Checks are assertions about the state of your application under test. They verify that certain texts, images, and other elements are visible on the page.


Make a trace that signs in to your application. After signing in, add a check that verifies that the user has been successfully signed in by checking for an element that is visible on the page after the sign in has completed successfully.

Adding checks

  1. When recording steps, select other steps from the pointer and then click check.

  2. Click an element on the page or highlight a text portion with your mouse in the Virtual Browser.

Check types

Select a check type by opening the locators from the check step. The following types are available:

Element Checks the element exists on the page defined by the step's locators.
Text Checks the text is found from the element defined by the step's locators.
Regexp Checks the regular expression matches the text in the element defined by the step's locators. Use when you need to check dynamic text. For example, text containing any number.
Javascript Checks the one-line Javascript expression evaluates to true. For more complex Javascript checks (with access to syntax-highlighted code editor), use the JS step.

How checks work

  1. Usetrace waits for the element defined in the step’s locators to be found. The maximum waiting time can be adjusted from the step’s locator tab.

  2. When the element has been found, Usetrace waits until the check condition (defined by the check type) is fulfilled. For example, an element’s text may change to the desired value after some delay.

  3. If the element is not found or the check condition is not fulfilled within the given time limit (default 15 seconds), the check fails.