Cross-browser validation is an important part of quality. In mabl, all tests run on Chrome by default. You can also configure tests to run on Firefox, Safari (WebKit) and Edge to ensure your website is working as expected across different browsers.
This article explains how to configure browser settings for test execution.
Plan runs
To edit browser settings for a plan, take the following steps:
- Click on the pencil icon to edit the plan.
- In the Browser devices settings section, select the browsers you would like the plan to run on.
- Save your changes.
Configuring browser settings for a plan
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.
Plan stage overrides
To override the default browser configuration for a specific stage in the plan, take the following steps:
- Click on the pencil icon to edit the plan.
- In the Tests section, click on Show tests.
- Click on the "Stage options" pencil icon for the stage you want to edit.
- In the Stage options panel, toggle on Override device settings for this stage.
- Select the browser(s) for tests in this stage.
- Save your changes.
Accessing plan stage options
Ad hoc test runs
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:
- Click on the Run test button to open the ad hoc run panel.
- Select the Cloud run tab.
- Choose the browsers you would like to run the test on.
- Add any other configurations as needed.
- Click Start run to trigger the test run(s).
Configuring browser settings for an ad-hoc run
Chrome only for local runs
mabl uses the Chrome app installed on your local machine for local test execution. However, it is possible to update the browser path to a different chromium browser, such as Microsoft Edge. See the article on updating the browser path for more details.