Other looping constructs can be used for the following sorts of examples (taken from the FAQs):
* "Wait until the text Loaded appears in the status bar"
* "If the checkbox isn't selected, then select it"
* "If this action isn't successful the first time, take some (or no) action and try again." The number of tries can be configured.
* "If this action isn't successful, then execute some other action(s)." The action(s) executed after the error can be any actions - for example taking a screenshot or restarting the application.
The Event Handlers are the items you will need to add this kind of logic to your tests. The following sections in the manual are worth reading:
There is also a cheat sheet in the ITE that deals with two examples of Event Handlers - the first example is for dealing with unknown statuses in the test (i.e. an error has occurred and the AUT should be cleaned up and the test started from the next use case). The second example deals with the "retry" Event Handler, which can be used to deal with known or planned deviations (i.e. the test should run successfully whether the save prompt dialog comes or not).
Further to this, we do also offer a specific training session in Event Handlers - you can contact our sales team if you're interested.