Local runs in the desktop app

Local runs were first introduced in the mabl CLI. These test runs execute local to your machine and allow you to get rapid feedback on your tests. Local runs are also available from the desktop app in both the Trainer and from the test details page.

These runs can be executed either headlessly or headfully. 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. Both types of local runs do not count toward your mabl cloud runs and are a great way to ensure your tests work as expected without interrupting your workflow.

Test Artifacts

Note that test artifacts - such as DOM snapshots or screenshots - are not captured from local runs. The mabl execution logs and final result are displayed in a separate window.

Headless local run executed from the test details page

Headless local run executed from the test details page

A local run can also be kicked off from the Trainer directly. 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 headful local run from the Trainer, simply save the test, click Play icon on the top toolbar, and select "Run test locally".

Local run from the mabl Trainer

Local run from the mabl Trainer

Limitations

Local runs from the test details page currently do not allow you to select a custom device for mobile web tests.

Running data table scenarios in local runs are not supported.

Updated 23 days ago


Local runs in the desktop app


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.