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 devices 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 Selecting 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/.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.
Known issues with Remote TestKit
If you run tests on Remote TestKit, the following errors may occur due to device or data center setting issues.
- The environment you requested was unavailable
- Failed to connect to /127.0.0.1:39503
- Could not install '/var/folders/0f/tvv_rcb90_xg96dfpk5dphvh0000gn/T/2023121-34136-1eif3ev.mjhp/********.app
- Could not find a connected Android device in 20055ms
- Unable to launch WebDriverAgent because of xcodebuild failure: xcodebuild failed with code 65
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 5. 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 in the Server URL field).