If a test fails on one browser but passes on another browser, you can take the following steps to isolate the issue:
Troubleshooting tests
This article focuses on troubleshooting browser-specific test failures. For more general advice on troubleshooting test failures, check out this article.
Review the test run history
Confirm whether the issue is indeed related to the browser. If there are previous passing runs on the browser that is currently failing, compare the passing runs with the failing runs to make sure the failure isn’t caused by a different issue, such as environment, DataTable scenario, or credentials.
Review test output
If you confirm that the issue is related to the browser, review the screenshots and logs for the steps leading up to the failing step to identify what happened.
Reproduce the same steps manually
Outside of the mabl Trainer, open the browser where the issue occurs and reproduce the test steps. If you can reproduce the same issue on the browser manually, the issue may be caused by browser compatibility in your app.
If you reviewed the test run history, confirmed that the issue occurs consistently for one browser, and cannot reproduce the issue manually, contact mabl support for further assistance.