Mobitru Plugin

The plugin provides integration with continuous testing cloud Mobitru.

Installation

  1. Copy the below line to dependencies section of the project build.gradle file

    Please make sure to use the same version for all VIVIDUS dependencies.
    Example 1. build.gradle
    implementation(group: 'org.vividus', name: 'vividus-plugin-mobitru')

  2. If the project was imported to the IDE before adding new dependency, re-generate the configuration files for the used IDE and then refresh the project in the used IDE.

Profiles

The plugin defines profile with a set of the preconfigured properties. In order to simplify work with Mobitru the plugin does following steps:

  1. Takes device.

    For the device search plugin relies on the capabilities specified in the properties.

    mobitru/web

    Use in conjunction with web application phone profiles.

    mobitru/mobile_app

    Use in conjunction with native mobile application profiles.
    Example 2. Capabilities to run tests on a specific device
    selenium.grid.capabilities.udid=ce22271b791f6c0603
    Example 3. Capabilities to run tests on any device with a specific platform version
    selenium.grid.capabilities.platformVersion=12
    Example 4. Capabilities to run tests on specific device model
    selenium.grid.capabilities.deviceName=iPhone 13

    For more fine-grained configuration of taking device additionally use Mobitru device search capabilities specified below.

    The properties marked with bold are mandatory.
    Property Name Acceptable values Description

    selenium.grid.capabilities.mobitru-device-search\:type

    phone or tablet

    The type of the device.

    selenium.grid.capabilities.mobitru-device-search\:manufacturer

    ZTE or samsung or IPHONE etc.

    The device manufacture name (case-insensitive).

    selenium.grid.capabilities.mobitru-device-search\:model

    SM-G930F or sm-s901b etc.

    The model of the device (case-insensitive).
    selenium.grid.capabilities.platformName and selenium.grid.capabilities.udid capabilities can not be specified along with Mobitru device search capabilities.
    Example 5. Capabilities to run tests on any SAMSUNG phone with a specific platform version
    selenium.grid.capabilities.platformVersion=12
selenium.grid.capabilities.mobitru-device-search\:type=phone
selenium.grid.capabilities.mobitru-device-search\:manufacturer=SAMSUNG

  2. Installs application on the device.

Properties

The properties marked with bold are mandatory.
Property Name Acceptable values Default Description

selenium.grid.username

The username.

<empty>

The name of the user.

selenium.grid.password

The access key.

<empty>

See guide section about the key.

mobitru.app-file-name

The name of application e.g. app.apk or app.ipa.

<empty>

The file name of the application under test uploaded to Mobitru. The application should be uploaded either via UI or REST API.

mobile-application.bundle-id

The valid application package name or bundle id.

<empty>

Package name for Android or Bundle identifier from Plist.info for iOS. It is used to activate the application under tests after Appium session start.

mobitru.resign-ios-app

true
false

true

(iOS only) Resign the application (*.ipa) with Mobitru profile or not.

mobitru.do-injection

true
false

false

Inject special code into application to allow emulation of "touch id" action and QR code scan.

mobitru.video-recording-enabled

true
false

false

Enable the video recording for entire appium session. The output recording will be attached to the report.

mobitru.device-wait-timeout

The duration in ISO-8601 Durations format.

PT5M

The timeout to wait while the requested device becomes available for usage. VIVIDUS will perform at most 20 retries during the timeout.