Multibrowser support

All about browser support in mabl

Cross-browser validation is an important part of quality. In mabl, all tests run on Chrome by default. Depending on your workspace's pricing plan, you can also configure tests to run on Firefox, Internet Explorer 11, Safari and Edge to ensure your website is working as expected across different browsers.


Internet Explorer sunset

Internet Explorer entered the end-of-support phase on February 1, 2023 and will be formally retired on October 1, 2023. Learn more about the Internet Explorer sunset plan here.

Mabl does not support Edge in IE mode at this time.

This guide describes cross-browser testing in mabl, including:

Configuring browser settings

At the plan level

On the Plans page, open the Plan Details page for the plan you would like to configure. Then take the following steps:

  1. Click on the pencil icon in the top left corner to open the Edit Plan page.
  2. Scroll down to Device settings.
  3. Choose which browsers you would like to run the plan on.

Configuring browser settings for a plan

  1. Click the Save plan button at the bottom of the page.


Adding browsers will increase runs

When a plan or test is configured to run on multiple browsers, the number of test runs increases proportionately.

For example, if you configure a plan with eight tests to run on three different browsers, each plan run will trigger up to 24 tests.

At the test level

You can also configure browser settings for ad hoc cloud runs. Open the Test Details page for the test you would like to run and take the following steps:

  1. Click on the Run test button to open the Ad hoc run panel.
  2. Select the Cloud run tab.
  3. Choose the browsers you would like to run the test on.
  4. Add any other configurations as needed.
  5. Click Start run to trigger the test run(s).

Configuring browser settings for an ad-hoc run

Browser-specific features

The following table identifies features in mabl that are only supported on specific browsers.

Feature(s)Supported browsersUnsupported browsers
Intelligent Wait, accessibility testing, and support for Shadow DOM testing, MFA logins, and right click steps*Chrome, Edge, Firefox Unified, Safari (WebKit)Firefox Legacy, Internet Explorer, Safari Legacy
PDF testingChrome, Edge, Firefox, Safari (WebKit)Internet Explorer, Safari Legacy
Mobile web testingChromeFirefox, Edge, Internet Explorer, Safari
Performance data and step traceChrome, EdgeFirefox, Internet Explorer, Safari
Visual change detection for browser testsChrome, EdgeFirefox, Internet Explorer, Safari
Console logsChromeFirefox, Edge, Internet Explorer, Safari
JavaScript snippet parametersChrome, Edge, Firefox, SafariInternet Explorer

*These features are only available for browser tests that can run on the Unified Runner.


Can I train browser tests against different browsers besides Chrome?

No, the mabl Trainer only supports training browser tests on Chrome. If you would like to see support for training tests on other browsers besides Chrome, please share your feedback in the mabl Product Portal.

How can I determine what browser version I am training against locally?

When you train a browser test, mabl uses the Chrome version installed on your computer. To check which version of Chrome you are using, visit chrome://settings/help.

How can I determine which browser version is used for cloud runs?

The following table lists the version used for each browser in cloud runs:

Firefox Legacyv91
Firefox Unifiedv108
Internet Explorerv11
Safari Legacyv15
Safari (WebKit)v16

To determine which browser version is used in test runs, hover over the browser icon in the test results or on the Test Output page. The version appears in a tooltip.


Checking the browser version on the Test Output page

When we update a mabl-supported browser for cloud executions, we share a post in the changelog.

What operating system do mabl-supported browsers use in the cloud?

BrowserOperating system
Chrome, Edge, Firefox, Safari (WebKit)Linux
Safari LegacymacOS
Internet ExplorerWindows

What is the maximum test run time on each browser?

The maximum run times for cloud runs are as follows:

  • Chrome, Firefox, Internet Explorer, Edge, Safari (WebKit): 6 hours
  • Safari Legacy: 1 hour

What is the maximum number of tests I can run in parallel on each browser?

The following table shows the maximum number of browser tests that can run in parallel at a given time on different browsers:

TypeTrial userCustomer
Chrome, Firefox, Edge, Safari (WebKit)101000
Safari Legacy1015
Internet Explorer1050

If you trigger more than the maximum parallel test run limit, the remaining tests have an on hold status until the other test runs finish. If you need higher concurrency, reach out to the mabl Support Team.

Which browsers are supported on the Unified runner?

Chrome, Edge, Firefox, and Safari (WebKit) are currently supported on the Unified Runner.

Which browsers are supported on the Legacy runner?

Firefox, Safari, and Internet Explorer are currently supported on the Legacy Runner.

Which browsers are supported for mobile emulation?

Mobile web testing is only supported on Chrome.

What can I do if a test is failing in one browser but not another?

When a browser test fails, reviewing the test output is always a good way to start investigating. Screenshots and logs for the steps leading up to the failing step can help you figure out what happened. If you observe that a test fails on one browser but passes on another browser, here are a few steps you can take to isolate the issue:

  1. 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.
  2. 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.
  3. Reach out to mabl support: 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 assistance.