|Methods of test execution / Multiple device execution|
Typical issues that you may encounter when executing tests on multiple devices, and possible solutions.
In some special cases, such as the test failing to find the target AUT (application under test), an automation exception occurs, causing execution on the device to be suspended, and an Automation Problem dialog box to appear:
The use device built-in action overrides any device specified in the Execute Test dialog box. For example, after selecting device A and clicking the Execute button on the dialog box, the test is executed on device A. The automated test runs on device A until it meets the action use device defined in the test procedure. At this time, the automation stops running on device A, and TestArchitect logically connects to device B and makes that device the target device for resuming the remaining automated test.