object wait probe

Description

The maximum wait time for a control to be available.

Value units

seconds

Default value

2

Notes

Result timeout

Unlike the usage of the object wait built-in setting where we expect the specified control must exist, the following built-in actions, such as if control exists, if control not exists, does control exist just want to know the existence of the control as a result for the next steps. The execution mechanism is explained as follows:
  1. TestArchitect starts looking for the specified window.
  2. If the specified window is not available, TestArchitect waits until the window is available within the default timeout 20 seconds, specified by the window wait built-in setting.
  3. When the timeout is reached but the window is still unavailable, TestArchitect reports a warning informing that the window could not be found (No pass or fail is recorded).
  4. If the window is found, TestArchitect starts looking for the specified control.
  5. With if control exists action:
    1. If the specified control is unavailable, TestArchitect waits until the control is available within the default timeout 2 seconds, specified by the object wait probe built-in setting.
    2. When the timeout is reached and the specified control is available, TestArchitect executes the if statement.
  6. With does control exists action:
    1. If the specified control is unavailable, TestArchitect waits until the control is available within the default timeout 2 seconds, specified by the object wait probe built-in setting.
    2. When the timeout is reached and the specified control is available, TestArchitect returns the value of 1.
  7. With if control not exists action:
    1. If the specified control is unavailable, TestArchitect waits until the control is available within the default timeout 2 seconds, specified by the object wait probe built-in setting.
    2. When the timeout is reached and the specified control is available, TestArchitect executes the else statement.