Methods of test execution
The are numerous methods of executing automated tests.
For power-saving purposes, computers are often configured to go into a non-active state (such as sleep) after a certain period of inactivity. By default, the processes associated with automated testing are typically not treated as “activities”, in this sense. Hence, for long execution runs, especially unattended ones, it is important that any machines serving as test controllers be configured not to lapse into any non-active mode during the test period. (Typically, your computer’s power policy is configured through its Control Panel, System Preferences, or command line, depending on the platform. For details, see your system administrator or information specific to the machine’s operating system.)
Configuring and running tests from TestArchitect Client
From a TestArchitect Client session, tests can be configured with the Execute Test dialog box.
Executing specific test cases
Specific test case(s) can be selected to execute within a test module.
Executing multiple test modules
There are several means of running multiple test modules sequentially within a test run.
Executing tests from the command line interface
With TestArchitect’s command line tool, tests can be launched from a command shell. When incorporated into batch files, the tool greatly extends the flexibility of test execution, especially from the standpoint of scheduling.
Remote test execution
The TestArchitect system allows you to launch a test on remote hosts and/or devices attached to the hosts, provided that each host has a TestArchitect Controller installed.
Multiple device execution
An automated test can be run on multiple devices attached to a local host, and/or on multiple controllers, and/or on multiple devices attached to the controllers.
Running tests with multiple remote desktop sessions
TestArchitect provides you the capability to execute tests with multiple remote desktop sessions.