Controller management

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).

The controller manages the execution of tests, with functions such as:

Working on the TestArchitect Controller dialog box

The TestArchitect Controller dialog box displays detailed execution information or compilation information that occurs on the local machine controller depending on whether you are executing or compiling a test.

To open the dialog box,

A drop-down list box in the dialog box contains the following information:

Naming convention for harnesses

The name of a harness is formed by combining the result name with the timestamp and request ID:

<Result name> (<timestamp>)- <request ID>

Tip:
If a harness' name is too long to be displayed fully, hover your mouse over this harness to view a tooltip of its complete name.

For example:

MultipleReservations (2018-07-03 11.09.47)- bmmtiq0jok0f

Where

Controller Settings
You can change controller settings via the TestArchitect Controller icon on the system tray.

Starting TestArchitect Controller
How to launch the TestArchitect Controller

Starting TestArchitect Controller from a command line interface
you are able to start TestArchitect Controller with a new port from a command line interface using either TAController or TACTRL command.

Changing a TestArchitect Controller port number
TestArchitect Controllers use a default port number of 53600. You can reassign a controller to any valid port number of your choice, so long as the port is not already in use.

Changing command line port
TestArchitect supports users in changing the TA command line port number to resolve port conflicts.

Related information

Connection retry configuration


Copyright © 2021 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