This page describes how to batch run tests in MagicPod.
If you want to run batch tests from the command line, see below.
- Run batch tests from the command line (Cloud environment)
- Run batch tests from the command line (Local PC environment)
Table of contents
- Run batch tests
- Run batch tests for multiple types of devices
- Schedule batch runs
- Run batch tests for specific test cases only
1. Run batch tests
In MagicPod, you can run all of the tests in the project as a batch.
To run them as a batch, select the Batch runs tab from the project screen, to move to the batch test run page.
To set the test target, click Details.
On the test run settings panel, specify the OS and an app to be tested, etc., and click Run new batch.
If you have already set up a test target, you can also run the batch by clicking Run new batch on the batch test run page.
When you select a cloud environment, the test will then start in cloud. When you select a local PC environment, MagicPodDesktop will launch and the test will then start in local. You will see that the test being run is added to the list on the batch test run page.
Once the test is completed, the success/failure status and execution time can be viewed in the browser.
Click the batch run number to the left of the list or > to the right of the list, and further confirm the results.
Click each test case number, and confirm the detailed test execution log.
If the test fails, you can confirm the error content and screen capture of the error.
Once the test is complete, all project members will be notified of the test results.
Reference: Notification of test results
2. Run batch tests for multiple types of devices
To run tests across different browsers or device versions/models, you can either add new run settings for each type, or add new patterns for each type within the run settings. We recommend trying the former method first.
2-1. Add new run settings for each type
First, click ︙ > Add new settings.
The following dialog will appear. Enter a preferred name, select Normal settings, and click OK.
Once the new run settings are added, specify the browser for each newly added run setting.
To run the tests, select the run setting that has the desired browser configured, and run it.
This will execute the batch run on the configured browser.
Note that this method will only perform a batch run of the tests on the single selected browser.
2-2. Add new patterns for each type within the run settings
As an alternative to method 2-1, you can also run batch tests across various browsers and device versions/models at once.
First, click ︙ > Add new settings.
The following dialog will appear. Enter a preferred name, select Multiple browser pattern settings, and click OK.
The new run settings will be added. As Multiple browser pattern settings was selected, two patterns are created by default.
To add more patterns, click Add.
Then, specify the browser for each newly added pattern.
To run the tests, select your newly added run setting and run it.
This will execute the batch run across the specified multiple browsers.
With this method, tests are executed in a batch run across multiple browsers at once.
Additionally, you can set parallel execution in Common settings. The maximum number of simultaneous parallel devices can be increased by adding options. For details, click here.
- In the case of Remote TestKit, a 10-minute waiting period may occur at the start of the test to process the return of the used device.
- By default, testing on the next device will not start until the test on the current device is completed. However, if you have a subscription plan with BrowserStack or Remote TestKit that allows parallel testing on multiple devices, you can set the number of simultaneous parallel tests in MagicPod, as shown in Figure 12. This will enable parallel test execution across multiple devices.
3. Schedule batch runs
You can automatically run tests in batch at a scheduled time. For more information, click here.
4. Run batch tests for specific test cases only
You can run only specific test cases instead of all test cases in the project. For more information, click here.