Configure tests for Android in online clouds
You can run Mobile Engine 3.0 TestCases using Android devices and emulators in online clouds. To configure these TestCases, you need to create specific test configuration parameters (TCPs) for each cloud. You can use the following online clouds:
For information on configuring TestCases for locally or remotely connected Android devices or emulators, see chapter "Configure tests for Android devices and emulators".
Generic TCPs
The table below contains the TCPs that are applicable for all Android devices and emulators.
Test configuration parameters |
Description |
Optional |
---|---|---|
Enter ChromeAndroid to automate hybrid and mobile web applications on Android. |
■ |
|
ExecuteInParallel |
Add this test configuration parameter on the ExecutionLists folder level and set its value to True to run your mobile tests in parallel. |
■ |
LiveView |
Live View enables you to display a preview of the Android device or emulator during test execution. To activate it, set the test configuration parameter LiveView to True. |
■ |
ScreenFlow |
If you want Tricentis Tosca to automatically save the screenshots of TestStepValues with ActionMode Input, set this parameter to True. For detailed information, see chapter "Take screenshots of TestStepValues with ActionMode Input". |
■ |
ScreenFlowPath |
Specify the path where you want Tricentis Tosca to save the screenshots of TestStepValues. For detailed information, see chapter "Take screenshots of TestStepValues with ActionMode Input". |
■ |
UseXBrowserForMobile |
As of Tricentis Tosca 13.2, the test automation of web applications is based on a new and fast mobile HTML engine. However, if you want to use the previous technology, add this test configuration parameter and set its value to True. |
■ |
Specify TCPs for Experitest
To run your TestCases on an Android device or emulator in Experitest, specify the test configuration parameters (TCP) as described in the table below.
Test configuration parameters |
Description |
---|---|
AppiumServer |
Enter https://cloud.seetest.io/wd/hub. |
DeviceName |
Enter the serial number of your Experitest device. This parameter is optional. Alternatively, you can set Desired Capabilities and use the capability Device Query introduced by Experitest. For more information on Device Query, refer to the Experitest documentation. |
ExperitestAccessKey |
Enter the access key of your Experitest account. To get the access key, follow the steps below:
|
ExperitestAppiumVersion |
Optionally, specify this parameter if you want to use a different Appium version than 1.16.0. The default Appium server version for Experitest test execution is 1.16.0-p2. |
In this example, you configure a test for a mobile web application in Experitest.
TCPs for iOS Experitest execution |
Specify TCPs for GigaFox (ex. Mobile Labs)
To run the test cases on an Android device or an emulator in GigaFox, specify the test configuration parameters as described in the table below.
Test configuration parameters |
Description |
---|---|
Enter the address of the GigaFox Appium server which by default is http://deviceconnect.yourcompany.com/Appium. Test automation requires Appium version 1.16.0. |
|
Enter the Device ID, which you can find in your device details view in GigaFox. |
|
Enter the access key of your GigaFox account. |
|
Enter the user name of your GigaFox account. |
To find your DeviceName, follow the steps below:
-
Log in to GigaFox.
-
Select Manage Your Account in the upper right corner.
-
Find the API Token section and click View Token. The DeviceName value is your deviceConnect ID in GigaFox, which you can take from your device details view.
Android Device ID in GigaFox
Example - Configure the TestCases on an Android device in GigaFox
In the example below, you configure a Shopping TestCase in an Android mobile web application for GigaFox.
TCPs for Android mobile web application in GigaFox |
Specify TCPs for Perfecto
To run the test cases on an Android device or on an emulator in Perfecto, follow the instructions in chapter "Configure tests in Perfecto".
Specify TCPs for Sauce Labs
To run the test cases on an Android device or an emulator in Sauce Labs, specify the test configuration parameters as described in the table below.
Test configuration parameters |
Description |
---|---|
Enter the address of the Sauce Labs Appium server. For the endpoint located in Europe, use https://ondemand.eu-central-1.saucelabs.com/wd/hub. For the endpoint located in the US, use https://ondemand.us-west-1.saucelabs.com/wd/hub. To avoid high latency, Tricentis recommends that you use the endpoint which is geographically closer to you. |
|
Enter the full name of the device or emulator that is accessible on Sauce Labs. |
|
Enter the version number of the Android device or emulator. |
|
To automate tests on Sauce Labs, enter the access key for your Sauce Labs account. You can find your access key in your Sauce Labs account information in the AccessKey section. |
|
To automate tests on Sauce Labs, enter the user name of your Sauce Labs account. |
Sauce Labs supports tests automation for the following subscription plans:
|
You can find a list of available Sauce Labs devices and emulators, as well as their names and versions in your Sauce Labs account or on the Sauce Labs Platform Configurator when selecting the Appium framework. |
Prepare native Android tests in Sauce Labs
To run native Android tests on devices or on emulators located in the Sauce Labs device cloud, follow the steps below:
-
Create a zip file out of your apk file.
-
Upload the zip file to Sauce Storage.
-
In Tosca Commander, import the Standard subset.
-
Drag and drop the Module Open Mobile App onto your TestCase.
-
Enter the zip file name into the Value column.
Open Mobile App Special Execution Task on Android
Example - Configure the TestCases on an Android emulator in Sauce Labs
In the example below, you configure a Shopping TestCase on an Android mobile web application for Sauce Labs. For the AppiumServer TCP, you use the endpoint which is geographically located closer to you.
TCPs for Android Sauce Labs execution |
Specify TCPs for TestObject
To run your mobile tests in TestObject, specify the following test configuration parameters:
Test configuration parameters |
Description |
---|---|
Enter the address of the TestObject Appium server. |
|
Enter the Device ID from your TestObject account. |
|
Enter the API access key for your TestObject account. |
Sign in to your TestObject account
-
Sign in to your SauceLabs account. TestObject is part of SauceLabs.
-
In the menu bar on the left, click on SAUCE APPS->Legacy RDC
Your TestObject account opens in a new tab.
Find your AppiumServer in TestObject
-
Click on the application that you want to test.
-
Click AUTOMATED TESTING and select Appium.
-
Click Setup Instructions.
Copy the Appium Server address that matches the location of your device.
Find your DeviceName in TestObject
To find your Device ID, follow the steps below:
-
Click on the application that you want to test.
-
Go to Live Testing.
-
Open the device that you want to use for your tests.
-
In the pane on the right, click INFO.
-
Copy the Device ID from the ID field.
Find your TestObjectApiKey in TestObject
To find your API Key, follow the steps below:
-
Click the Account icon and select Account Settings.
-
Copy the API Key from the User API Key field.
Example - Configure the TestCases on an Android device in TestObject
In the example below, you configure a Shopping TestCase in an Android mobile web application for TestObject.
TCPs for Android TestObject execution |