verifyDoesNotExists

This is a pre-built Action located under the @Custom Element. The functionality of this Action in Avo Assure is to verify whether the specified object is not present on the web page. The result is stored in the given dynamic variable for further use during test execution.

The verifyDoesNotExists action works only when the VerifyExists action is executed in a preceding step.

Syntax

Input Value: <ObjectType>;<VisibleText(optional)>;<Index>;<abs(optional)>

Argument	Description
<ObjectType> (Required)	Provide the object type you want to verify for existence in the application.
<VisibleText> (Optional)	Provide the visible text associated with the object.
<Index> (Required)	Provide the position of the object you want to identify based on its sequence in the application. Note: Index start from 0.
<abs> (Optional)	Provide the absolute XPath of the object you want to identify for this operation.

Note:

• If the last argument abs is defined, the action executes using absolute identification based on the specified absolute XPath provided in the input.

• To skip an optional input value, use an extra semicolon (;).

Output Value: <Dynamic Variable>(Optional);<Dynamic Variable>(Optional)

Argument	Description
<Dynamic Variable>(Optional);<Dynamic Variable>(Optional)	Both variable stores the status of as True or False.

Example 1: Verifying Non-Existence of an Object

In this example, we are explaining how to verify that a specified object does not exist on the application interface.

• Action: verifyDoesNotExists

• Input Value: Button;;0

  • The first argument (Button) specifies the object type to be identified.

  • The second argument is left blank to skip an optional value.

  • The third argument (0) specifies the index of the object when multiple matching elements are present.

• Output Value: {Status}

  • The result of the verification operation is stored in the {Status} dynamic variable with the following possible values:

    • True: If the specified object does not exist on the application interface.

    • False: If the specified object exists.

• Logical Explanation: The verifyDoesNotExists action reads the identification details from the Input Value column (Button;;0). The action searches for the specified object using the object type, visible text, and index. If the object is not found on the application interface, the verification result is stored as (True) in the {Status} variable.

Example 2: Verifying Non-Existence of an Object using Optional Parameter

In this example, we are explaining how to verify that a specified object does not exist on the application interface using optional parameter.

• Action: verifyDoesNotExists

• Input Value: Button;Delete;0

  • The first argument (Button) specifies the object type to be identified.

  • The second argument (Delete) specifies the visible text associated with the object.

  • The third argument (0) specifies the index of the object when multiple matching elements are present.

• Output Value: {Status}

  • The result of the verification operation is stored in the {Status} dynamic variable with the following possible values:

    • True: If the specified object does not exist on the application interface.

    • False: If the specified object exists.

• Logical Explanation: The verifyDoesNotExists action reads the identification details from the Input Value column (Button;Delete;0). The action searches for the specified object using the object type, visible text, and index. If the object is not found on the application interface, the verification result is stored as (True) in the {Status} variable.