Troubleshooting multiple device execution

Typical issues that you may encounter when executing tests on multiple devices, and possible solutions.

Handling automation problems during concurrent testing on multiple devices.

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:

At this point, you can click the Debug button in the Automation Problem dialog box to enter debug mode.

Tip: 

What happens if, in the Execute Test dialog box, we have specified that the test is to execute on device A, but the test procedure itself invokes built-in action use device to specify that execution is to take place on device B?

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.


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