Test automation is managed by the TestArchitect Controller application, which interacts with and obtains vital test run information from the interpreter. A machine on which TestArchitect Controller is running is referred to as a controller.
In addition to managing an automated test on a local application, or on one or more devices connected to the controller machine, the TestArchitect Controller software on a given machine can manage multi-station testing in which it directs the activities of one or more deputy controllers.
The TestArchitect Controller software can manage automated testing of a local application, or of an application running on one or more devices connected to the controller machine. In addition, TestArchitect Controller on a given machine can manage multi-station testing, in which one or more deputy controllers are directed in their test activities, in either a serial or parallel synchronous mode of execution, also known as lead-deputy.
From the standpoint of the host OS, the controller is a service (or daemon). A dialog box is available that allows you to view the test execution log of your local controller, as well as any others to which your machine is connected.
When the TestArchitect Controller dialog box appears, it shows detailed execution information that occurs on the local machine's controller. To view execution information for a device actively running a test, select that device from the drop down device list and the execution information is appended to the end of the information list. Refer to Test Results to learn how to view terminated execution test results for devices attached devices.