Mobitru Plugin

The plugin provides integration with continuous testing cloud Mobitru.

Installation

Copy the below line to dependencies section of the project build.gradle file
Example 1. build.gradle
```
implementation(group: 'org.vividus', name: 'vividus-plugin-mobitru', version: '0.5.4')
```
If the project was imported to the IDE before adding new plugin, 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:

Waits for the requested device to be available using REST API call and takes it in the usage.
Installs application on the devices using REST API call.

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

Properties

The properties marked with bold are mandatory.

Property Name Acceptable values Default Description

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.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.

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.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.