Configure local or remote test automation

For a simplified setup and configuration of local and remote devices, we recommend that you install Tricentis Mobile Agent. It allows you to quickly and seamlessly connect and test iOS devices on Windows, Mac, and Linux.

You can run your Mobile Engine 3.0 tests on the following types of devices:

Android devices or emulators connected locally to your PC.
Android devices or emulator connected to a remote Mac, Windows, or Linux machine.
iOS devices connected locally to your PC.

iOS devices or simulators connected to a remote Mac, Windows, or Linux machine.

You must create test configuration parameters (TCPs) that are specific to your mobile platform and the type of connection.

This chapter lists all available TCPs for local or remote test automation.

It also has detailed information on mandatory TCPs for each:

"Specify TCPs for emulators, Android, and iOS devices connected locally"
"Specify TCPs for emulators, simulators, Android, and iOS devices connected remotely"

Overview of TCPs for local or remote test automation

The table below lists all available TCPs for local or remote test automation.

Mobile TCP	Local Android	Remote Android	Local iOS	Remote iOS
TMAServer	■	■	■	■
Browser (hybrid and web app)	■	■	■	■
DeviceName	■	■	■	■
OSVersion	■	■	■	■

For a list of all mobile TCPs, see chapter "Mobile TCPs overview".

Specify TCPs for emulators, Android, and iOS devices connected locally

To run tests on emulators, Android, and iOS devices connected locally, specify the following TCPs:

Mobile TCP	Description
TMAServer	Add this TCP to specify the Tricentis Mobile Agent server address. You don't need to specify the TMAServer TCP if you automate locally connected iOS and Android devices or emulators.
DeviceName	Add this TCP to specify an Android device or emulator on which you want to execute your mobile tests. Set its value to the ID of your Android device or emulator. You don't need to specify the DeviceName TCP, if you connect only one Android device to your computer. Alternatively, if you don't want to provide the name of your device, you can enter the OSVersion TCP instead. For detailed information, see chapter "Specify the DeviceName TCP".
OSVersion	Enter the version of your Android operating system. Tricentis Tosca automatically runs the tests on a device that matches this parameter. Specify this TCP if you don't want to provide the exact ID of your device.

Mobile TCP

Description

TMAServer

Add this TCP to specify the Tricentis Mobile Agent server address. You don't need to specify the TMAServer TCP if you automate locally connected iOS and Android devices or emulators.

DeviceName

Add this TCP to specify an Android device or emulator on which you want to execute your mobile tests. Set its value to the ID of your Android device or emulator.

You don't need to specify the DeviceName TCP, if you connect only one Android device to your computer.

Alternatively, if you don't want to provide the name of your device, you can enter the OSVersion TCP instead.

For detailed information, see chapter "Specify the DeviceName TCP".

OSVersion

Enter the version of your Android operating system. Tricentis Tosca automatically runs the tests on a device that matches this parameter.

Specify this TCP if you don't want to provide the exact ID of your device.

In this example, you configure a test for a mobile web application on an Android device connected locally.

You specify the Browser TCP, because it's mandatory if you test mobile web applications.
You specify the DeviceName TCP, because you connect multiple Android devices and you want to run your tests on a specific one.

TCP for a mobile web application on an Android device

Specify TCPs for emulators, simulators, Android, and iOS devices connected remotely

To run tests on emulators, simulators, Android, and iOS devices connected remotely, specify the following TCPs:

Mobile TCP	Description
TMAServer	Add this TCP to specify the Tricentis Mobile Agent server address when you are connected remotely. You don't need to specify the TMAServer TCP if you automate locally connected emulators or iOS and Android devices connected via USB.
DeviceName	Add this TCP to specify an Android or iOS device, or a simulator on which you want to execute your mobile tests. Set its value to the UDID of your Android or iOS device, or simulator. For detailed information, see chapter "Specify the DeviceName TCP".
OSVersion	If you want to use simulators for specific iOS versions, enter the respective iOS version number as a value.

Mobile TCP

Description

TMAServer

Add this TCP to specify the Tricentis Mobile Agent server address when you are connected remotely. You don't need to specify the TMAServer TCP if you automate locally connected emulators or iOS and Android devices connected via USB.

DeviceName

Add this TCP to specify an Android or iOS device, or a simulator on which you want to execute your mobile tests. Set its value to the UDID of your Android or iOS device, or simulator.

For detailed information, see chapter "Specify the DeviceName TCP".

OSVersion

If you want to use simulators for specific iOS versions, enter the respective iOS version number as a value.

In this example, you configure a test for a native application for a remote iOS device.

You specify the DeviceName TCP, because you connect multiple devices and you want to run your tests on a specific one.
You specify the TMAServer TCP, because you want to run your test with the Tricentis Mobile Agent.

TCPs for a native application on a remote iOS device

In this example, you configure a test for a mobile web application for a remote Android device.

You specify the DeviceName TCP, because you connect multiple devices and you want to run your tests on a specific one.
You specify the TMAServer TCP, because you want to run your test with the Tricentis Mobile Agent.
You specify the Browser TCP, because it's mandatory if you test mobile web applications.

TCPs for a mobile web application on an Android device