Continuing on, we shall explain the basic method of creating a test using the mobile app test version of MagicPod.
- Daily build + batch test run schedule settings
- Create MagicPod batch run settings
- Set up test results email notification
- Set up test results Slack notification
- Test run schedule settings (for Bitrise)
- Test run schedule settings (for CircleCI)
- Features for ease of use
1. Daily build + batch test run schedule settings
Once you have created several tests, you can schedule them to run as a build + batch test every day, and configure the results to be sent using email or Slack notifications.
1-1. Create MagicPod batch run settings
First, set up MagicPod for a batch run.
Click Details in the Batch runs tab in the project you wish to configure.
From Settings name in the upper left corner, either select an existing setting or add a new one.
Set Environment to Cloud and App Type to Cloud upload *1.
1-2. Set up test results email notification
To configure email notifications, click Common settings and set the Notify test result by email option to Enabled. (The default is to provide notifications.)
1-3. Set up test results Slack notification
To configure Slack notifications, click Common settings and set the Notify test result by Slack option to Enabled. Then, you'll see Add, so click it.
When the popup window appears, input your desired name and click Add to Slack.
Select the channels for which you wish to send notifications, and click Allow.
For the method of setting whether to provide notification(s) of Success/Failure/Requires Confirmation/Suspension, see Set up test results notification.
1-4. Test run schedule settings (for Bitrise)
First, create a build configuration for Bitrise to create an App file from the source code according to the procedure in How to create an App file - 1. When using Bitrise
1-4-1. Run MagicPod tests from a Bitrise build
Link Bitrise and MagicPod. Open Bitrise’s Workflow Editor.
Press the “+” button below the “Xcode build for simulator” step,
and search for the MagicPod step to add.
Once added, click Enter value and set each item.
- MagicPod API token
- Set the values copied from MAGIC_POD_API_TOKEN in Key and the MagicPod API token page in Value, and click Add new.
- Organization name
- Specify the organization name used in MagicPod. Note that this is not the display name, but the name in alphabet characters used by the organization URL. )
- Project name
- Specify the project name used in MagicPod. Note that this is not the display name, but the name in alphabet characters used by the project URL. )
- Test settings number
- Specify the number of the settings created in 1−1. Create MagicPod batch run settings
Although there is a wide variety of other parameters available, it will still work with these other parameters in their default value state*2. Apps built in Bitrise are uploaded to the MagicPod side as well, and tests will be run at the time of CI.
When finished, save the modifications,
move to the build screen,
and run the build again.
Once the test finishes successfully,
in addition to the Bitrise test result email,
the MagicPod test results email will be sent.
After adjusting the settings, the following types of tests will be possible.
- Tests can be run in parallel in multiple device patterns for uploaded apps.
- Change the uploaded app from an app file to an IPA file and test the app you have built on an external Cloud service such as SauceLabs/BrowserStack on an actual device
1-4-2. Run Bitrise builds periodically
Click Start/Schedule a Build at the top-right of the Bitrise build screen.
The build configuration pop-up window will be displayed, so enable the Schedule this Build switch.
Specify the time, day of the week, and branch you want to build, and press Start Build after selecting the Workflow you just created.
This completes the build schedule setup.
1-4-3. Trigger a build for every Push or Pull Request to the repository
If Webhook is set in the initial settings, the build will be automatically run whenever there is a Push or Pull Request to the Git repository. This timing can be adjusted using the following method.
- You can adjust the timing of the build start, such as Push and Pull Requests from the Workflow Editor Triggers tab *3.
- Build results are automatically linked to screens such as GitHub, and this makes it easy to check build results in response to Push and Pull Requests.
- Displaying build results in relation to Push requests
- Displaying build results in relation to Pull requests
1-5. Test run schedule settings (for CircleCI)
CircleCI works in conjunction with MagicPod to schedule builds and test runs.
Refer to the following for details on the setup method.
2. Features for ease of use
If you wish to know all the commands, see Command list.
FAQ and tips for operation in the early stages of installation are presented in Tips for initial introduction (Mobile App).
- Method of operating screens for which scrolling is required
- Email tests
- WebView tests
- Utilization of shared steps No limit on the number of creations
- Utilizing variables
- Utilizing conditional branching
- Visual diff checks
- Innovations in application implementation to simplify automated testing
- Run only specific test cases as a batch
- Mobile app test frequently asked questions
*Notes / Sources
- Since the apps to be tested are uploaded from Bitrise, the settings made for the batch execution settings screen are not relevant.
- By changing the settings, you can select whether to wait until the test is complete or whether to delete the apps uploaded to the MagicPod after the test is complete.
- Starting builds
Next, we shall explain the screens and terms used for the various settings.