Internally, there is no significant difference in behavior between a single run and a batch run. Therefore, it is highly likely that the test is unstable or failing due to the influence of tests run before the target test. If you want to confirm whether the batch run is the true cause, please run only the failing test as the target multiple times in the batch run and check if it fails.
Additionally, we recommend identifying the cause using the Failure Analysis feature and attempting fixes based on the suggestions from MagicPod Autopilot.
Possible causes and solutions
- The launch option is set to "by first-time-only process restart" and the process remains, so tests run before the target test are affecting it
- Set the launch option to "by process restart" to prevent previously run tests from affecting the current test. (Please see Command list)
- Batch run is not the direct cause, but the test is unstable
- Improve stability by changing locators or adding wait commands. For details, please refer to Improving test stability
- Test run settings differ between single run and batch run
- Check if the same test run settings are being used.