Remote TestKit is a Web service that can be used with various real devices on the Cloud, and there is a rich lineup of devices available within Japan. It is useful to check the behavior of a mobile application on various devices before its release.
Table of Contents
- Compatible models/OS version
- Method of use
- Command line execution
- Batch test execution for multiple types of devices
- Return the device after the batch test run
- Limitations
- How to Use in Case of the Remote TestKit Enterprise (On-Premises Plan)
Compatible models/OS version
You can check this here. There are numerous types of devices available for use within Japan.
Note that the number of standby units of each type is limited, and there may be times when you cannot perform tests because the devices have been borrowed by other users.
Method of use
First, apply for a trial account via the Remote TestKit consultation form. (figure 1)
Figure 1. Remote TestKit consultation form.
When the trial account is issued, enter the necessary items, as shown in figure 2, on the batch test execution screen.
Figure 2. Remote TestKit test execution settings.
[1] Access tokens
Log in to the Remote TestKit site from the Login page, and click the ▼ icon next to the account name.
Next, open the Access token settings, and copy the access token.
Figure 3. Access tokens.
[2] Target OS
This supports both Android/iOS.
[3] OS version/device name
If you log in to the Remote TestKit site from the Login page, the available devices will be displayed in the Device list. Enter the model name/OS version (figure 4) of the device you wish to use on the MagicPod screen.
Figure 4. Model name/OS version.
- As the rental process is performed automatically, there is no need to perform the rental on the Remote TestKit page.
- The device you are currently using for the automated test is displayed as “currently loaned out.”
- The types of device that are available for the trial version are limited.
-
You can specify the model name/OS version using a partial match like "iPhone" for the model. For details, see Selecting a Device in the Appium link tutorial. To reduce errors caused by temporary device unavailability, we recommend using the partial match settings.
For example, if you specify "Pixel 10," it will run on any available device in the Pixel 10 series, including "Pixel 10 Pro" and "Pixel 10 Pro XL."
[4] Target type
For Android, if you want to test your local APK file, choose .apk/.aab file (cloud upload) to upload the APK file to the cloud.
If you want to use DeployGate or TestFlight to directly download an APK file from a specific URL, choose .apk/.aab file (URL).
This is the same for iOS IPA files.
Command line execution
Using this method, you can also perform batch test execution from the command line.
Batch test execution for multiple types of devices
Using this method, it is possible to run batch tests for multiple types of devices at once.
Return the device after the batch test run
By default, devices used in a batch test run are retained for 10 minutes after completion. To immediately start a new batch test run on a different device, select "Immediately after tests" in the Return device settings. Conversely, to run consecutive batch test runs on the same device, select "Keep for 10 minutes after tests".
Limitations
External cloud services can only be used during batch test runs. When creating or editing test cases, please select "Cloud" or "Local PC" (Reference).
You may not be able to operate the Settings app. For more details, please check here.
How to Use in Case of the Remote TestKit Enterprise (On-Premises Plan)
The way this is used differs slightly in case of the Remote TestKit Enterprise (On-Premises Plan).
Figure 5. Remote TestKit Enterprise(On-Premises) test execution settings.
[1] Cloud service name
Select Remote TestKit (On-premises).
[2] Authentication information
it is necessary to enter the access token and the Appium Server URL. If you use username and password, please switch to access token because username/password authentication will be deprecated in a future release. Furthermore, in the case of Remote TestKit Enterprise, it is necessary to prepare the Appium Server that can be accessed from the MagicPod side (IP: 52.196.146.190) in advance (specify this URL in the Server URL field).