Wait times for various commands and UI interactions during test execution

When you are running an automated test on a web based application, accelQ applies implicit wait times to let the application page or field become ready for interaction. This behavior is different for each 'type' of command as listed below:

Interaction commands

Example: Click, Enter Text in element etc.

If the element is not found, waits for the timeout specified in the "Element timeout" attribute in Run modal.

Control and tuning of this wait time is at test execution level.

Wait commands

Example: Wait for Element, Wait Until Element Enabled etc.

If the element is not found or if the required criterion (such as 'enabled') is not met, waits for the amount of time specified as part of the command.

Control and tuning is at the Action logic statement level.

Verify commands

Example: Verify Element Text, Verify Element Exists etc.

If the element is not found, or if required criterion is not met, waits for the timeout specified in the "Element timeout" attribute in Run modal.

Control and tuning at test execution level.

Enquiry commands

Example: Is Element Exists, Is Element Enabled etc.

No wait time is applied. Command returns immediately without waiting for any amount of time. Use these commands only when you are performing conditional logic when you are sure the page is fully loaded. If you want to wait a reasonable period before using this command, make sure to put wait-for type of command before this.

Note: If your logic requires to throw an error message or abort the test case if a particular element does not exist, make use of wait-for command with appropriate setting, instead of using an enquiry command.