Starting Android automated tests
Approaches to selecting which Android device(s) run automated tests in TestArchitect.
You can specify which Android device runs a given automated test, or portion of a test, from either your test launch command (online or offline) or from within your test procedures.
Test initiation, which is typically performed either from the Execute Test dialog box or via a test execution batch file, specifies which device or devices test execution starts on. Once testing begins, your test procedure can control where execution is to take place, using the built-in action use device. For example, after you’ve selected device A in the Execute Test dialog box and clicked the Execute button, your test is executed on device A. The automated test runs on device A until it encounters the action line use device B in the test procedure. At this time, the automation stops running on device A, and logically connects to device B, making that the target device for the remainder of the automated test. This is basically the same as synchronous serial execution in desktop testing.
Note that synchronous parallel execution is also possible in mobile testing. It involves the same mechanism as used for desktop testing, requiring that the lead/deputy method be used to pass control between controller-device clusters (controllers hosting mobile devices).
Running automated tests on mobile devices using capabilities file
Running automated tests on mobile devices using capabilities file is a great way to run your test on multiple devices and reduce the time it takes to maintain your test. Here’s a quick post on how to run automated tests on mobile devices using a capabilities file.
Selecting multiple devices at launch time
This post explains how to run automated tests on mobile devices using built-in actions, which allows for easy switching between devices and specifying which device to use for test modules.
Tel:
Email: