![]() ![]() ![]() To run native Android tests on devices or on emulators located in the Sauce Labs device cloud, follow the steps below: Prepare native Android tests in Sauce Labs 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. To automate tests on Sauce Labs, enter the user name of 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 access key for your Sauce Labs account. To avoid high latency, Tricentis recommends that you use the endpoint which is geographically closer to you.Įnter the full name of the device or emulator that is accessible on Sauce Labs.Įnter the version number of the Android device or emulator. 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.Įnter the address of the Sauce Labs Appium server.įor the endpoint located in Europe, use. To run the test cases on an Android device or on an emulator in Perfecto, follow the instructions in chapter "Configure tests in Perfecto". TCPs for Android mobile web application in GigaFox To open the command prompt, click the Start button and enter cmd into the search box.Įnter adb devices into the command line to display the IP address and port. To find the IP address and port that serves as the DeviceName, follow the steps below: For detailed information, see chapter "Find DeviceName in Genymotion". You can verify if the Appium server address works correctly by opening it in a browser.Įnter the IP address of the virtual device created by Genymotion and the port on which ADB operates. The Appium server address consists of the IP address of your PC or Mac, the default Appium port 4723, and the standard path of the Appium server /wd/hub. To do so, start the server manually and enter the Appium server address. If you automate an Android emulator in Genymotion remotely, you need to specify the AppiumServer test configuration parameter. If you automate an Android emulator in Genymotion locally, you don't need to specify the AppiumServer test configuration parameter. To run the test cases on an Android emulator in Genymotion, specify the test configuration parameters as described in the table below. Specify the path where you want Tricentis Tosca to save the screenshots of TestStepValues. ![]() If you want Tricentis Tosca to automatically save the screenshots of TestStepValues with ActionMode Input, set this parameter to True.įor detailed information, see chapter "Take screenshots of TestStepValues with ActionMode Input". To activate it, set the test configuration parameter LiveView to True. Live View enables you to display a preview of the Android device or emulator during test execution. The table below contains the TCPs that are applicable for all Android devices and emulators.Įnter ChromeAndroid to automate hybrid and mobile web applications on Android.Īdd this test configuration parameter on the ExecutionLists folder level and set its value to True to run your mobile tests in parallel. You can use the following online clouds:įor information on configuring TestCases for locally or remotely connected Android devices or emulators, see chapter "Configure tests for Android devices and emulators". To configure these TestCases, you need to create specific test configuration parameters (TCPs) for each cloud. You can run Mobile Engine 3.0 TestCases using Android devices and emulators in online clouds. Configure tests for Android in online clouds ![]()
0 Comments
Leave a Reply. |