Table of contents
- In the case of a batch run
- In the case of a local PC test on the test case edit page
- In the case of a cloud test on the test case edit page
In the case of a batch run
Click the Abort button. Note that the Abort button is only displayed to users with Update test cases permission.
If the execution does not stop after pressing the Abort button, a hang-up may be occurring. In this case, the status will automatically change to Failed after approximately 12 hours. Please contact MagicPod Support if you cannot run a new test because there are not enough devices (browsers) to run the cloud test due to this effect.
How to Check the Number of Devices (Browsers) Available for Cloud Tests
You can view the number of available cloud devices (browsers) on the Batch Run page.
Additionally, you can check the number of cloud devices (browsers) currently in use on your organization's Usages page. However, only users with Organization Update Permission have access to the Usages page.
In the case of a local PC test on the test case edit page
If the test stops moving forward while it is still running, you can abort the test by pressing the “x” button to the right of the “Running” button. In addition, the test may remain running due to a temporary glitch. In that case, please try the following procedure.
- Close MagicPodDesktop.
- Reload the Edit test page.
- Run the test again.
You can now run a new test. The previous test will remain in running status, and this will not be affected. Tests that stay in the Running status will automatically change their status to Failed after approximately 12 hours.
In the case of a cloud test on the test case edit page
If the test stops moving forward while it is still running, you can abort the test by pressing the “x” button to the right of the “Running” button. In addition, the test may remain running due to a temporary glitch. In that case, please try the following procedure.
- Close the device.
- Relaunch the device.
- Run the test again.
You can now run a new test. The previous test will remain in running status, and this will not be affected. Tests that stay in the Running status will automatically change their status to Failed after approximately 12 hours.