The maximum wait time for a window to become available or, depending on the action involved, unavailable.
- The window wait setting is applicable to nearly every built-in action that contains the window argument. This built-in setting is used when it is expected that the specified window must exist.
- However, the window wait setting is not applicable to does/if built-in actions, that is, if window exists, if window not exists, and does window exist. Instead, the window wait probe setting is used for those three built-in actions.
- Setting a high wait time value may negatively impact test performance.
- For web automation, window wait goes into effect first, and then page wait does. In other words, TestArchitect first looks for the presence of the specified window; once that condition is satisfied, TestArchitect waits the allotted page wait time for the web page to be rendered and available.
- TestArchitect starts looking for the specified window.
- With the check window exists action:
- If the specified window is not yet available, TestArchitect waits until the window is available within the default timeout of 20 seconds, specified by the window wait built-in setting.
- When the timeout is reached but the window is still unavailable, TestArchitect issues a Failed report.
- With the check window not exists action:
- If the specified window is available, TestArchitect waits until the window is unavailable within the default timeout 20 seconds, specified by the window wait built-in setting.
- If the timeout is reached but the window is still available, TestArchitect issues a Failed report.