ATEasy call end events as the last processing step for a module, task or a test. Some uses for this event include writing test results to the Test Log, deciding which procedure to run next based on test results, and deactivating electrical power to systems. Termination events are processed after equivalent initialization events.
Termination events are processed in the reverse sequence of the initialization events as shown in the following table:
|
Module |
Event |
When Processed |
Usage Examples |
|
Program |
As the last action before a test ends. |
Output text to the Test Log describing the results of the tests or decide which step to do next based on the test results. |
|
|
Driver(s) |
As the last action before a test ends. The events are processed in the reverse order of the drivers listed. |
For a test executive driver, modify and close the user interface based on user input or the results of the last test. |
|
|
System |
As the last action before a test ends. |
Output text to the Test Log describing the results of the tests. |
|
|
Program |
As the last action before a task ends. |
Output text to the Test Log describing the results of the tests. |
|
|
Driver(s) |
As the last action before a task ends. The events are processed in the reverse order of the drivers listed. |
For a test executive driver, modify and close the user interface based on user input or the results of the last test. |
|
|
System |
As the last action before a task ends. |
Output text to the Test Log describing the results of the tests. |
|
|
Program |
As the last action before a program ends. |
Output text to the Test Log describing the results of the tests or the conclusion of the program. |
|
|
Driver(s) |
As the last action before a program ends. The events are processed in the reverse order of the drivers listed. |
For a test executive driver, modify and close the user interface based on user input. |
|
|
System |
As the last action before a program ends. |
Output text to the Test Log describing the program. |
|
|
Program, then Drivers(s) then System |
OnEndSwitchUut (v8) |
Depends on the App.UutSwitchLevel, may be called after a program, task or a test completion. |
cleanup after UUT program, task or test completion, redirect to next UUT index. |
|
System |
As the last action before the system and driver processing is completed. |
If necessary, reinitialize driver. Use driver to set instrument to a known state before program ends. |
|
|
Driver(s) |
As the last action before the driver processing is completed. The events are processed in the reverse order of the drivers listed. |
Perform any final termination processes for the instrument driver after the application has finished using it. For a test executive driver, close the user interface. |
|
|
System |
After everything else. |
Perform any termination processes for the entire application after drivers are terminated. Output text to the Test Log describing the completion of the application. |