Add verification steps

Add verification steps to check your application as the script progresses. This helps you identify whether your application is functioning correctly. You can add verification steps in the editor, the step editing pane, and from the AI Inspect window.

Types of verification steps

Verification steps can check any of the following:

  • The existence, state, or value of objects in your application.

  • The value of an input or output parameter.

  • The visible content of the application's current screen.

If the condition specified in the Verify or Smart Verify step is not met, the step fails.

Note: To evaluate AI-generated responses in your application, use an Evaluate GenAI response step. This step lets you customize the metrics and pass levels used to check how well the response meets your expectations. For details, see using Evaluate GenAI responses.

The following table describes the verification types supported by Verify steps.

Verification type Description
Verify the existence of an object

The verification step checks whether an object exists or does not exist in the application.

This may be helpful, for example, to make sure an object is present before performing an operation on it.

Verify the state of an object

For AI objects such as checkboxes, radio buttons, and toggles, you can add a verification step that checks the state of the object.

Depending on the type of object, you can verify whether the object is checked, not checked, selected, not selected, on, or off.

Verify the value of an object

For AI objects with a string value, you can add a verification step that checks the value of the object.

Objects with a string value, include, for example: buttons, text boxes, fields, or input objects.

The value of a button is the text on the button.

The value of a text box and other input fields is the text inside the box.

You can verify the following about a value: 

  • Whether the value is empty or not.

  • Whether the value is or isn't equal to a specified string.

  • Whether the value contains, or is contained within, a specified string.

Verify the value of a parameter

For input or output parameters, you can add a verification step that checks the current value of the parameter.

You can verify whether the value is empty or not, and whether it is or isn't equal, containing, or within a specified string.

Smart Verify using Aviator

Use a Smart Verify step to check any of the following: 

  • The value of an AI object that has a string value. For example, a button, text box, field, or input.

  • The value of a parameter.

  • The content of the application's current screen. Current screen refers to the visible area of the application. You can check anything about the screen's content.

Smart Verify steps are powered by Aviator and let you describe any condition you want to verify using plain text.

You can describe the condition in plain language, without going into technical detail. For example, you could have a step that verifies the validity and relevance of a date range or email address, or a step that makes sure all items displayed on the screen are of a certain type.

You can include script parameters in the condition by typing @ and then selecting an existing parameter from the list or clicking + New parameter to create one.

The following example demonstrates some Smart Verify steps:

Copy code
Smart Verify that the value of "Date" editfield is earlier than @NextYear and follows the DD/MM/YYYY format
Smart Verify the value of "Email" input is a valid email address and is part of the opentext domain
Smart Verify the current screen all items are on sale
Smart Verify the current screen only earrings are shown

AI objects and property-based objects

Verify steps on AI objects and property-based objects work differently.

Verify steps on AI objects

Verify steps on property-based objects

The existence of AI objects is checked only in the visible area of the application.

By default, verification steps do not scroll the application to locate the object. This ensures that the application remains in the same state at the end of the step. If necessary, you can override this behavior using the step settings. For details, see Customize settings.

The existence of property-based objects can be detected anywhere on the application page.

The verification step does not scroll the application to make the object visible. The object can be detected even if it is not currently visible in the application.

Write a verification step

You can add a verification step in the editor by typing it or using an initial step template.

To add a verification step in the editor: 

  1. Click the Add step button .

  2. Select the Verify or Smart Verify option. The step template is added to the script.

  3. Modify the template following the syntax rules described in Step syntax.

    Tip:  

    • For Smart Verify steps on objects, make sure to select an Object class that has a string value. Otherwise, the step action reverts to a plain Verify.

    • To check a parameter, replace "<FIELD_NAME>" <CLASS> with @<parameter name>. After you type @, you can select an existing parameter from the list or click + New parameter to create one.

Build an object verification step

Use the UI elements in the step editing pane or the AI Inspection window to build a step verifying an object's existence or value.

To build an object verification step: 

  1. Select an object for your step:

    • During inspection, click an object highlighted by the inspection.

      A pop-up with the suggested step and object description opens.

    • In the step editing pane, select an Object class from the list.

  2. Select the Verify or Smart Verify action.

  3. Select the condition for the step:

    • For a Smart Verify step, enter a free-text description of the condition you want to verify.

      To use a parameter in the condition, type @ and select an existing parameter from the list or click + New parameter to create one.

      When you run the script, Aviator compares the object's value in the application with the condition you describe.

      (Optional) If you are adding the step during inspection, click Test to see whether your description matches the current value of the object. This helps make sure your condition works well. The test returns a detailed explanation about the match, facilitating any necessary adjustments.

    • For a Verify step, select a condition.

      Condition Description
      Exists

      (Default) The step succeeds if the object exists.

      Does not exist

      The step succeeds if the object does not exist.

      The object's state. Select from the available states.

      The step compares the object's state with the state you select, and fails if the condition is not met.

      The available states depend on the object type. For example, On, Off, Selected, Unselected.

      Value of

      The step compares this object's value with the value you specify.

      During inspection, click Edit step in pane and continue in the pane that opens.

      To configure the value to compare:

      1. Select a string comparison condition from the list.

      2. Enter a constant value or click the Use script parameter button to use a parameter.

  4. To add the step to the script from inspection, click Add step.

Build a parameter verification step

Use the UI elements in the step editing pane to build a step verifying a parameter's value.

To build a parameter verification step: 

  1. In the step editing pane, select an Object class from the list and select the Verify or Smart Verify action.

    • For a Verify step, you can select any object class.

    • For a Smart Verify step, select an object that has a string value, such as button, text box, field, or input.

    You can also add a Verify or Smart Verify step in the editor and then continue in the step editing pane.

  2. In the Target area, click the Parameter button to switch from AI Object to Parameter.

    Note: When you switch between the AI Object and Parameter options, the step is reset to a template. To undo, use CTRL+Z.

  3. Select an existing parameter from the list or click + New parameter to create a new parameter.

  4. Configure the value to compare with the selected parameter's value:

    Step type Value to compare
    Verify

    Select a string comparison condition from the list and specify the value to compare.

    Enter a constant value or click the Use script parameter button to use a parameter.

    Smart Verify

    Enter a free-text description of the condition you want to verify.

    To use a parameter in the condition, type @ and select an existing parameter from the list or click + New parameter to create one.

Build a current screen verification step

Use the UI elements in the step editing pane to build a Smart Verify step that verifies the content of the application's current screen.

To add a smart verification step on the current screen: 

  1. In the editor, start a new step and type smart verify.

  2. In the step editing pane, in the Target area, click the Current screen button to switch from AI Object to Current screen.

    Note: When you switch between the AI Object and Current screen options, the step is reset to a template. To undo, use CTRL+Z.

  3. Specify the condition for the step:

    • Enter a free-text description of the condition you want to verify.

    • To use a parameter in the condition, type @ and select an existing parameter from the list or click + New parameter to create one.

Set step configuration options

In addition to specifying what the verification step checks, you can set additional options in the step editing pane.

Tip: To open the Edit step pane during inspection, click the Edit button in the dialog box that opens when you click a highlighted object.

Option Description Default
Timeout

For a step verifying an object's existence.

Enter the number of second to wait for the step's condition to be met.

20
Stop test run upon failure

Select if you want the test run on the current application to stop when the verification step fails.

If selected, an indicator Stop is added to the step in the editor.

The step failure is reported but the run continues.

See also