Skip to main content

Ad hoc test runs

Eva Ferreira
  • Updated

You can run a single test ad hoc to get quick feedback on a test and confirm that everything is working as expected. This article explains how to trigger ad hoc runs in the mabl app, including how to…

mabl CLI

Click here to learn how to trigger ad hoc runs from the mabl CLI.

Triggering a local ad hoc run

A local run executes on your machine and does not count toward your quota of allotted credits. To trigger a local ad hoc 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.
  3. In the ad hoc run panel, select Local run.
  4. Configure settings for the local ad hoc run.
  5. Click on the Start run button.

A window containing log output opens for each test execution. Local run output does not persist inside the mabl app.

local_run_output.png

Output for a local run

Triggering a cloud ad hoc run

A cloud run executes on mabl's highly secure and scalable infrastructure. To trigger an ad hoc run in the cloud, 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.
  3. In the ad hoc run panel, select Cloud run.
  4. Configure settings for the cloud ad hoc run.
  5. Click on the Start run button.

To view test output, click on the test run that appears below the Start run button.

ad_hoc_view_output_en.png

Triggering a single test from the mabl Trainer

If you are editing a browser 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 play icon at the top.
  3. Select "Run test locally" to run the test locally. Select "Run test in cloud" to run the test in the cloud.

trainer_run_cloud.png

If you run the test in the cloud, you can find the status in the Results tab of the test details page. Click on the result to view the test output for that specific run.

Note

When triggering an ad hoc run from the Trainer, mabl uses the settings associated with the training session. If you want 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 instead.

Limitations of ad hoc runs

While triggering a single test is suitable for simple troubleshooting and verification purposes, running tests ad hoc come with some limitations.

Test diagnostics

The following information is not collected for ad hoc runs:

These features are only available for tests run as part of a plan.

Default tests

mabl does not support triggering ad hoc runs of the following default mabl tests:

  • "Visit all linked pages within the app", also known as the link crawler
  • "Visit home page"

Related articles