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 mabl Trainer and from the Test Details page.

These runs can 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.

Both types of 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.

The Local Run Output window

The mabl execution logs and final result are displayed in a separate 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 or screenshots - are not captured from local runs.

Triggering a local run during a training session

Browser and API tests can both be run 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.

Browser tests

To launch a headful local run from the Trainer, save the test, click the play icon on the top toolbar, and select "Run test locally".

API Tests

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.

🚧

Limitations

• Running DataTable scenarios in local runs is not supported.
• For browser tests, local runs from the Test Details page currently do not allow you to select a custom device for mobile web tests. Tests will use the default device configurations stored for the test.