Critical wait settings

The critical wait settings (window wait, page wait, object wait, item wait and property wait) are those which are used for conditions and preconditions which, if not satisfied, result in a warning or failing of a test.

In some cases, the condition/precondition you are testing is something of a show-stopper: if it is not satisfied, the action either cannot complete execution and must report a warning (for preconditions), or must report a fail for the test (for check…exists conditions). The timing settings for these critical waits are:

The example below demonstrates three critical wait settings - window wait, object wait and item wait - used as timers for preconditions of the get table cell value action. When executed, the action first looks for the presence of the View Orders window; if it must wait for the window to appear, that wait is governed by the window wait timer. A timeout results in a warning for the test, whereas discovery of the window allows the action to proceed to its next stage. A similar case is true for the next two stages of finding the specified object (a table), and the specified item (a specific cell of the table).

This action, get table cell value, also uses the non-critical timing setting value changed wait. For purposes of this topic, that is ignored here, but is discussed later.

Copyright © 2024 LogiGear Corporation. All rights reserved. LogiGear is a registered trademark, and Action Based Testing and TestArchitect are trademarks of LogiGear Corporation. All other trademarks contained herein are the property of their respective owners.

LogiGear Corporation

1730 S. Amphlett Blvd. Suite 200, San Mateo, CA 94402

Tel: +1 (650) 572-1400