Wait times for various commands and UI interactions during test execution

When you run an automated test on an application, ACCELQ applies implicit wait times to ensure the application screen or field is ready for interaction.

The wait times for various command types are detailed below:

Interaction Commands

Examples: "Click", "Enter Text in Element", etc.

If the element is not found, these commands wait for the timeout specified in the "Element Timeout" attribute in the Run modal. This wait time control is set at the test job level.

Wait Commands

Examples: "Wait for Element", "Wait Until Element Enabled", etc.

Use these commands if the default element timeout is insufficient, especially for slow-loading elements. You have complete control over the maximum timeout value, which is specified as an argument for these commands.

Verify Commands

Examples: "Verify Element Text", "Verify Element Exists", etc.

If the element is not found, or if the required criterion is not met, these commands wait for the timeout specified in the "Element Timeout" attribute in the Run modal. This wait time control is set at the test job level.

Condition Check Commands

Examples: "Is Element Exists", "Is Element Enabled", etc.

These commands check if a particular element is visible or in a specific state, typically used for writing conditional logic. There are three timeout options for these commands:

• None: The commands return the result immediately without waiting.
• As Per Run Settings: Waits based on the test job level element timeout value.
• Custom: You can specify the amount of time to wait for the condition to be met.