Remote TestKit is a Web service that can be used with various real devices on the Cloud, and there is a rich line-up of devices available within Japan. However, when automated tests are run on a daily basis, it is difficult to obtain stable results due to various errors and usage restrictions, so we do not actively recommend their use. (There seems to be no problems when using it for manual tests. )
Compatible models/OS version
You can check this here. There are numerous types of terminals available for use within Japan. However, as there are not so many standby units of each type, there may be times when you cannot perform tests because they 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
Download the Remote TestKit software version, and copy the access token displayed in “Manage access token” (Figure 3) on the “Menu” button.
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. For details, see “Specifying a Device” in the Appium link tutorial. When specifying the Android model name/OS version, note that there are known issues.
[4] Target type
For Android, if you want to test your local APK file, choose “APK 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 File (Specify 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.
Running tests in relation to multiple types of devices as a batch
Using this method, it is possible to run batch tests for multiple types of devices at once.
Known issues with Remote TestKit
If you run tests on Remote TestKit, the following problems may occur.
- Due to Remote TestKit restrictions, if multiple Android devices with the exact same model name and version are used, and a device reboot occurs due to some reason during the test, there is a risk that the device being used may switch to another one midway through. There is also the same risk when the name of the device partially matches the name of another device. For example, as there is only one device named “Pixel 3a XL,” at first glance it would seem that there is no risk of switchover. However, as this name partially matches the name of a separate terminal “Pixel 3a XL - dark,” there is a risk this may switch midway through.
- The device will automatically be returned once 10 minutes have passed since the end of the test, but the same device will not be able to be used for the next 30 minutes. If you try to use the same device, the error “The environment you requested was unavailable” shall occur. Requests are currently being made to MagicPod support to rectify this problem.
- Additionally, the error message “The environment you requested was unavailable” may occur due to device or data center setting issues. If there is no additional error information other than this, please contact MagicPod Support or Remote TestKit Support, as the problem is most likely on the Remote TestKit environment side.
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 3 Remote TestKit Enterprise(On-Premises) test execution settings
[1] Cloud service name
Select Remote TestKit (On-Premises)
[2] Authentication information
With the Remote TestKit Enterprise (On-Premises Plan), as access tokens are currently unavailable, it is necessary to enter the Appium Server URL, username and password. 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 as “Server URL”).