On this page, we shall explain the procedure for creating and running tests in the local PC environment.
Table of Contents
- Create test cases
- Specify the target OS/app
- Acquire screen captures
- Create test procedures
- Run test cases
- Tests across multiple screens
1. Create test cases
First, click the Edit test case button to move to the test case edit page.
Figure 1. Edit test case button.
On this page, we will create the detailed content of the test case.
Figure 2. Test case edit page.
2. Specify the OS/app
First, launch the app and acquire information, such as screen captures, etc. To do this, it is necessary to specify the OS and app in the test run settings panel, and connect to the device.
Figure 3. Test run settings panel.
*Here, we will explain how to specify the iOS test when using the simulator. For Android, we describe the Android real device + apk file test and Android real device + installed app test methods.
For iOS, set the following.
- OS: iOS
- App Type: .app file
Then, in the Enter full path to .app file field, specify the full path of the app file, which is the app entity.
The full path of the app file can be copied by right-clicking the app file while holding down the option(alt) key and clicking Copy "********" as Pathname.
Figure 4. Copy "********" as Pathname of the app file.
Once configured, click Connect.
Figure 5. Connect button.
3. Acquire screen captures
Select Open MagicPodDesktop when the browser confirmation dialog box shown in figure 6 is displayed.
Figure 6. Browser confirmation dialog box.
MagicPodDesktop will then launch.
After a short wait, MagicPodDesktop will launch the iOS simulator on the PC, and the app will be installed and launched.
Figure 7. Image of app launching on the iOS simulator.
Once the connection is made, click Capture UI by desktop app.
Click this to acquire a screen capture. Once you click this button, the capture upload and scan will start, and after a short amount of time, the test case edit page will be displayed.
The screen capture can be directly dragged & dropped, and uploaded to the test case Edit page. However, in this case, the function to edit automatically-recognized screen names, which will be described later, will not be available, so this is not recommended at this time.
Figure 8. Screen capture displayed on the test case edit page.
At this point, we have acquired the screen capture.
More precisely, the app UI tree information has been uploaded in addition to the screen capture.
4. Create test procedures
As we have uploaded one capture, we can perform a simple test using just one screen. By selecting, and dragging & dropping elements on the capture, you can easily create a test procedure as shown. Using the element selection mode, elements can also be added by clicking.
Figure 9. Test procedure.
The content of the commands can be changed freely, as shown. A wide variety of commands are provided, so check the Command list page for detailed information.
Figure 10. Command switchover.
Additionally, the element name is automatically generated using AI, but in case the generated name is inappropriate, you can change the name by clicking on the relevant area on the screen capture.
Figure 11. Change the element name.
MagicPod, in addition to the element name, also holds the system information of the element, which is used to identify elements during test execution.
5. Run test cases
Once the test procedure is created, click Run at the bottom of the test case edit page.
Figure 12. Run button.
As shown in figure 13, you can see that the app is launched and automatically operated by the iOS simulator. The test execution log is displayed in real time on MagicPodDesktop for each step.
Figure 13. Image of test run.
If the test succeeds, Success is displayed for the execution button.
Figure 14. Image of successful test.
Click Details to see the test results.
Figure 15. Screenshots.
Figure 16. Test run log.
Figure 17. Appium log.
Figure 18. Test run information.
6. Tests across multiple screens
When creating tests across multiple screens, it is necessary to acquire screen captures for each screen.
For example, when configuring the screen for the iOS test app, just now, as 1.Main screen screen has already been acquired, it is necessary to acquire the capture screens for 2.Completion of registration screen and 3.Alert screen.
Figure 19. Test app screen settings.
To acquire the captures in 2 and 3, first operate the app, open the screen in 2 with the iOS simulator, return to the browser, and click the Add UI button.
Figure 20. Add UI button.
When you do this, the Capture UI by desktop app button will be displayed again, so click this to capture the screen in 2.
Figure 21. Capture UI by desktop app button.
You can capture other screens while waiting for the scan, so switch the iOS simulator screen to 3 during the scan and, on the browser once more, click Add UI > Capture UI by desktop app, to capture the screen in 3.
Once the scan is complete, you can create a test while switching the screen capture using the UI List button.
Figure 22. UI List button.
In this way, you can create multiple screen tests.
Figure 23. Test the multiple screens you have created.