On this page, we will explain the procedures for creating and running tests on various combinations of local PC environments.
Table of Contents
- Android real device + apk file test
- Android real device + installed app test
- iOS real device + ipa file test
- iOS + installed app test
1. Android real device + apk file test
The procedure for creating and running tests using an actual Android device and an apk file, which is the substance of the Android application, is generally the same as for iOS. However, the method of specifying the target OS/app and the method of acquiring screen captures are slightly different from those for iOS.
If you are using an apk file, specify "Android" as the target OS with a target type of "APK file" and specify the full path to the apk file. (Figure 1)
Figure 1 Specifying the target OS and app for Android
The apk file path is the same as in case of iOS, so right-click the apk file, press the option key, and acquire using “Copy as Pathname”. (Figure 2)
Figure 2 Copying the apk file path name
Next, before pressing the button to connect to the device, connect the Android real device to the PC with the USB cable. Unlock the device. Furthermore, the Allow USB debugging dialog box will appear (Figure 3), so press OK to allow debugging.
Figure 3 Allow USB debugging dialog box
After connecting the device, if you press the Connect button (Figure 4) on the Edit test case page, and wait for a while, the apk file app will be installed on the real device, and the app will launch.
Figure 4 Button to connect to Edit test case page
You can then acquire the screen capture, and create and run the test for this app.
Figure 5 Tests created in relation to the apk file app
Incidentally, if the same operation is performed while the Android emulator is launched, it will also be possible to actually perform the test using the Android emulator.
2. Android actual device + installed app test
With the MagicPod, it is also possible to test apps installed on the Android real device (the apk file is also unnecessary and it does not need to be our own app). In this case, you can specify the tested app using the “Package/activity” system information. (Figure 6)
Figure 6 Package/activity
The “Package/activity” value in the app can be looked up using the following method.
- Connect the Android real device to the PC using the USB cable.
- Set the target OS to “Android”, leave the “Package/activity” value blank, click the “Connect” button on the Edit test case page, and connect to the device.
- Once the connection is established, operate the device manually, and launch the app to be tested.
- Open the target specified pop-up window on the Edit test case page, and click the “Acquire app information”. If you wait for a while, the “Package/activity” information for the app being launched will be set. (Figure 7)
Figure 7 Acquire “Package/activity” for app being launched
Once you acquire the “Package/activity” information and connect to and launch the specified app with this information, you can acquire screen captures, create tests, and run tests.
3. iOS real device + ipa file test
If you are using the iSO real device and the ipa file that is the content of the iOS app to run the test, specify the following values for the test target.
- For “OS”, enter “iOS”
- For “Device Type”, enter “Real device”
- For “Team ID”, enter Apple developer program team ID
- Full path to the ipa file on your PC in "IPA file”
Figure 8 Method of specifying the iOS real device + ipa file test
By simply connecting the iOS real device to the PC using the USB cable, you can acquire the screen capture and run the test.
- Unlock the device.
- As the confirmation dialog shown in Figure 9 is displayed, tap the “Trust” button.
- If you encounter other errors that prevent you from connecting to the device or running the test, try this workaround.
Figure 9 iOS real device confirmation dialog box
iOS/iPadOS 16 real devices require enabling developer mode.
4. iOS + installed app test
With MagicPod, it is possible to test apps installed on the iOS simulator or on a real device (neither the app file or ipa file are necessary, and it does not need to be our own app). In this case, you specify the app to be tested with the system information called "bundle ID". (Figure 10)
Figure 10 Bundle ID
It is possible to look up the app bundle ID using the following method.
- In case of an app published on the Apple App Store, these can be looked up by entering the name of the app or the App Store page URL on the Bundle ID Finer
- A list of bundle IDs can be found here for the apps that are installed on the device.
If you encounter other errors that prevent you from connecting to the device or running the test, try this workaround.