Aborting a program calls an OnAbort event. OnAbort events are used mainly to ensure that Units Under Tests (UUTs), instruments, and programs are shut down in an orderly manner. Some ways in which this event is called include when a manually run program is stopped by an ATEasy menu command or when a running program processes an Abort statement.
OnAbort events are processed in the sequence shown in the following table:
Module |
Event |
When Processed |
Usage Examples |
Program |
When a Program encounters an Abort condition. The user may wish to output text to the Test Log. |
Shut down the UUT. |
|
Driver(s) |
When a Driver encounters an Abort condition. The events are processed in the reverse order of the Drivers listed. |
For a test executive driver: prompt the user to start another program or close the application; start another program in the application; clean up and save the log. |
|
System |
When the System encounters an Abort condition. |
Shut the instrument down. |