Select a device and launch a manual session on the Kobiton Portal’s
- iOS: ITA only supported iPhone with iOS version 11+
Install an application from Apps Repo
- The ITA will only be triggered on list of apps that have already been uploaded into the App Repo
- Apps uploaded from “Upload File” or “Install from URL” are currently not supported
Perform some manual test steps (at least 1 step)
Now you can do the manual execution again on Kobiton device to prepare the test case, which is going to be an input (test step) for the automated test on multiple devices.
- There are some limitations regarding to test steps (please visit the section “ITA’s Limitations” section below)
Select the device bundles
You are all set! After exiting this manual session, you will encounter with the pop-up for the select a device bundles for the automated testing. Your manual test case above will be used to re-run on these selected set of devices.
Currently, ITA could be triggered on any Kobiton Android devices but we recommend to run with the option “Top 10 Global” for the best stability
In case you don’t receive the pop-up for selecting the device bundles, you might have violated some limitations of ITA (unsupported test actions, some corner cases that ITA does not supported yet, etc.). We are sorry for this inconvenience, you will need to perform a manual session again.
See the ITA’s result
Behind the scenes, Kobiton will do preparation for the process of running a massive number of devices. The process will take around an hour before generating a list of automated sessions from ITA. After that, you will receive an announcement email for informing the successfully starting process.
In the Session List:
No. Description 1 The manual session that you just performed the test The system will base it on the defined groupID to generate the automation test sessions.
Note: In this case, users performed manual test on the device: Xperia XZ Premium - Android 8.0.0
With manual sessions that triggered ITA, there are always 2 new icons displayed within a session’s row
From left to right:
1.1: Re-run ITA
1.2: Execution List
1.1 You can trigger the process of running on multiple devices to run again
Note: Right now ITA allows you to run on the same devices that you have been selected. In the future, ITA will give you another ability to re-run on other sets of devices.
1.2 The execution is just another place where you can manage and keep track of all automated sessions’ status.
You can find more information about the Execution List in the next section 5.2 below
2 The list of automated sessions that Kobiton automatically revisited on other multiple devices based on the manual session at #1
Note: In this case, users select the bundle of 20 global devices
- Sometimes you will see the error icon within the manual session’s row, which means there are some problems with the process of generating automated sessions. For this situation, you can either use the re-run icon or you can directly contact us for support at: email@example.com
In the Session Details:
By the time, in the session details of the manual session triggered ITA, you will see there are test steps with purple, which mean those are the qualified test case for ITA. Other steps will be considered as normal test steps within a manual session and will not be executed for ITA.
The “borderline” between qualified ITA test steps and nonqualified is the ‘ITA Interrupted’, the reason might be some unexpected errors occurred like device and network issues or you might have violated some current ITA unsupported actions.
Don’t worry! Your qualified test steps will be executed properly for ITA. In case, you want to have a test case more properly, you can perform another test or you can send the sessionID for us to troubleshoot at: firstname.lastname@example.org
The execution list is another ‘place’ that helps you to manage and keep track of every automated session, which is generated by ITA. You can access the execution list via the Execution List icon within manual session’s row.
Execution Status Description Passed Successfully revisit on a selected device Failed Failed to revisit on a selected devices
Note: There are many issues that lead to the Failed status:
- Device not available
- Device's problems: network, cpu, etc.
A device is not support the installed app
You can access the session details for specific failed session to see the problem in more detail.
Enqueued The revisit has been enqueued and is waiting for the execution Running The revisit has been triggered Blocked The revisit has been blocked due to ITA can not find an element to select to continue a revisit. For the next action on this status, please see the section “Remediation” below
Note: This state of status is different with Failed, the revisit is not failed yet, but there are some issues that blocking the process of test steps during the execution.