Running browser and API tests locally
Local runs of browser and API tests execute local to your machine and allow you to get rapid feedback on your tests. Local runs do not count toward your mabl cloud runs, and they are a great way to ensure your tests work as expected without interrupting your workflow.
Triggering a local run
You can trigger local test runs from the mabl Desktop App or the mabl CLI.
In the Desktop App
On the Test Details page, click on Run test, configure your test run in the Local run tab, and click Start 1 run.
You may also run browser and API tests locally during a training session. This is especially useful if you are actively making changes to a test and would like to verify that they work without leaving the training session.
To launch a local run from the mabl Trainer, save the test, click the play icon on the top toolbar, and select "Run test locally."
To trigger a local run from the API Test Editor, save the test and click the play icon in the top left corner of the window.
In the mabl CLI
Use the mabl CLI command
mabl tests run to trigger a local test run.
For browser tests, local runs do not allow you to select a custom device for mobile web tests. Tests will use the default device configurations stored for the test.
Headful vs. headless runs
Local runs of browser tests may be executed either headfully or headlessly.
- A headful local run will launch the browser on your machine and output the execution logs for the test in a command-line style window.
- A headless run will not launch the browser on your machine, as these tests run in the background. Only the window with the test execution logs and the final result will appear during a headless run.
Local run output
For a local test run, mabl execution logs and results are displayed in a separate test output window:
Logging for local test runs
Unlike cloud runs, the logs for local test runs do not persist in the mabl app. Test artifacts, such as DOM snapshots and screenshots, are not captured from local runs.
Updated 21 days ago