Ad hoc test runs

Ad hoc runs can be triggered at the test and plan level. Triggering tests manually is useful when you want to get quick feedback on a test and confirm that everything is working as expected.

Trigger a single test via the UI

You can trigger a single test to run locally or in the cloud. For more information on triggering local runs in the desktop app, check out this guide.

If you would like to trigger an ad hoc cloud run, take the following steps:

1. Navigate to the Test Details page of the test that you want to run.
2. Click on the "Run Test" button. A modal will appear with two options: local run and cloud run.

3. Select the Cloud run tab.
4. Add any additional configurations as needed, such as URL override or credentials. If you're using mabl Link for a cloud run, make sure you run against an environment with an active link connection.

5. Click the "Start 1 run" button.

📘

Default mabl tests

Triggering ad hoc runs of the following default mabl tests is not supported:

• Visit all linked pages within the app (link crawler)
• Visit home page

Trigger a single test from the mabl Trainer

If you are editing a test and want to check if your changes are working properly, you can trigger a cloud run of the test you're editing right from the mabl Trainer:

1. Save your changes.
2. Click on the plan icon at the top.
3. Select Run test locally or Run test in cloud. The status for a cloud run can be found in the Results tab of the Test Details page. Clicking on the result will take you to the Test Output page for that specific run.

📘

Limitations

When triggering a cloud run from the Trainer, mabl will use the settings associated with the training session. If you would like to add any additional configurations, such as a URL override or credentials, or run it in a different environment, we recommend that you trigger the run from the Test Details page, where these settings can be configured.

Identifying ad hoc test runs

The Test Output page for a test that was triggered manually shows "Ad hoc run" in the plan section:

Limitations of ad hoc test runs

While triggering a single test is suitable for simple troubleshooting and verification purposes, running tests in this fashion come with some limitations:

• Custom headers cannot be specified.
• The following observations are not collected for ad hoc test runs:
  • Auto-healing logic
  • Insights
  • Speed index
  • Coverage information
• On Legacy runs, step trace is not generated.

Running mabl tests from the CLI

Using the mabl CLI, you can trigger ad hoc test runs locally (including headless runs) and in the cloud. For more info on the mabl CLI, click here.

Triggering a plan via the mabl UI

See the article on triggering plan runs for more information.