Mobile Modules

In this example, you apply the Desired Capabilities skipServerInstallation and skipDeviceInitialization to reduce the startup time of Android test execution.

In this example, you run your TestCase on multiple cloud providers and dynamically modify the capabilities. At the same time, you keep a set of shared capabilities that apply across all providers. To do so, you use both the Set Desired Capabilities and Add Desired Capabilities Modules.

When you run your tests on Tricentis Device Cloud (TDC), you set your Desired Capabilities to customize your tests as follows:

• Wait up to 300 seconds before timing out, because you want to give your tests enough time to finish, if there are delays due to the device or network.

• Select a random device from the cloud pool for testing, because you want to test a variety of devices. This helps catch device-specific issues and gives you broader test coverage.

• Disable device screenshots, because you want to speed up test execution time by skipping unnecessary screenshot captures, especially when you don't need visual verification.

• Configure the device to restart at the start of each session, because you want to ensure a clean environment for each test run, avoiding issues from leftover processes or data.

When testing on native apps, you add a Desired Capability to specify the app ID, which ensures the correct app launches on the device, while also applying the previously defined capabilities.

Without the Add Desired Capabilities Module, you would need to use the Set Desired Capabilities Module. This would require you to manually reconfigure the previous capabilities to include the app ID. Building your capabilities piece-by-piece makes your test setups smoother, more flexible, and less prone to errors.

Set Desired Capabilities and Add Desired Capabilities Modules in a TestCase

In this example, you perform the following actions:

• You open the mobile application with the Module Open Mobile App.

• You click on the button Show SnackBar With Delay, which triggers the snackbar.

• You use ActionMode WaitOn to wait until the snackbar with the text message Speed changes everything appears.

• You verify whether the message is Speed changes everything.

• You click the button on the snackbar to close it.

In this example, you perform a tap gesture at 10% of the x-coordinate and at 50% of the y-coordinate from the top left corner of the screen.

In this example, you download the file example.png from your Android device to your computer.

In this example, you draw a simple shape with three swipe movements. Each movement lasts one second.

In this example, you perform the following actions:

• You start a new Appium session and open the URL http://sampleapp.tricentis.com/101/app.php.

• You interact with the mobile controls on the screen.

• In the End Appium Session TestStep, you use the Module End Appium Session to end your current Appium session.

• You start a new Appium session and interact with the same screen.

In this example, you verify if the driver script returns the property username with the value testuser1.

In this example, you save the Appium session ID to a buffer named SampleBuffer.

In this example, you press the Back button on Android.

In the example below, you set the screen orientation to Landscape.

In this example, you open the mobile application with the Open Mobile App Module by specifying the PackageName and the Activity of the application you want to steer.

In this example, you send text input to a dynamic search field.

• The Focused Control TestStep sets the focus on the dynamic search field.

• The next TestStep uses the Send Text Input To Focused Control Module to send text input to the search field.

• After the search, a drop-down list appears with results that match your search query. The Destination Airport TestStep selects the correct result from the drop-down list.

In this example, you disable the default auto-hide mode of the onscreen iOS keyboard.

In this example, you perform the following actions:

• You open the mobile application with the Module Open Mobile App.

• You enable biometric authentication on your iOS simulator. In the TestStep Set iOS biometrics enrollment, you set the ModuleAttribute State to True.

• In the Click the Login button TestStep, you click a button which triggers an action that requires user authentication.

• In the TestStep Use iOS biometric authentication, you set the type of user authentication to TouchID.

• To trigger positive authentication, you set the TestStepValue Positive authentication to True.

In this example, you perform an upward swipe that lasts 1 second.

In this example, you perform the following actions:

• You open the first mobile application with the Module Open Mobile App.

• You click on a screen position in the first application.

• You switch to the second mobile application with the Module Switch Mobile App.

• You click on a screen position in the second mobile application.

In this example, you perform the following actions:

• You open the mobile application with the Module Open Mobile App.

• In the Click the Login button TestStep, you click a button that requires user authentication.

• In the TestStep Use Android fingerprint authentication, you specify the fingerprint ID. If you have set the same ID on your emulator, the authentication is positive. Consequently, the TestStep passes.

In this example, you perform the following actions:

• You open the mobile application with the Module Open Mobile App.

• You enable biometric authentication on your iOS simulator. In the TestStep Set iOS biometrics enrollment, you set the ModuleAttribute State to True.

• In the Click the Login button TestStep, you click a button which triggers an action that requires user authentication.

• In the TestStep Use iOS biometric authentication, you set the type of user authentication to TouchID.

• To trigger positive authentication, you set the TestStepValue Positive authentication to True.