Taking action on problems

You can provide TestArchitect with specific instructions as to what to do when a problem occurs.

In many cases when an error or test failure occurs, it is necessary not just to interrupt the normal flow of processing, but to take some specific action or set of actions. Such actions might include:

Two actions serve this purpose:

The action that you specify may be a built-in action, but in most cases it is likely that you will want to call a dedicated user-defined action to handle the error or failure.

As an example, the following is a simple error handler that, when called, merely writes out a report to the effect that an error occurred, and captures the screen at the time of the error, saving it to a designated jpg file:

A test module that uses this handler is shown below:

The on error action action specifies the error handler. (Note that on error action need not necessarily be limited to the INITIAL section of the test module, and you are not limited to specifying a single error handler within the test module. Indeed, it is possible to have on error action calls scattered throughout your action lines, so that the appropriate handler is invoked for each given place in which an error is possible.)

Copyright © 2023 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(800) 322-0333