Run Tests Remotely
Start remote runs from the console, on a schedule, or via the API
Remote runs execute your tests on SmoothDeploy's cloud infrastructure. There are four ways to trigger them.
From the Console
Single Test
- On the Tests page, click the blue Run button on any test row.
- Review and override the run config in the dialog.
- Click Run Test.
The same Run button is available in the test editor toolbar.
Bulk Run
- Select multiple rows on the Tests page.
- Click the Run (play) icon in the bulk toolbar.
- Adjust config in the dialog and confirm.
Draft tests in a bulk selection are excluded. A warning toast names how many will be skipped.
A run can include at most 100 tests. Folders count as the tests inside them, and draft tests do not count. If you select more than 100 tests, the Run icon is disabled.
Config Overrides
Both dialogs show a config form. Changes here apply only to this run and do not modify the test's saved config. Select a Config Preset to prefill the form. See Config Presets.
Schedules
A schedule triggers a run automatically at a set time. Create and manage schedules under Operations → Schedules in the sidebar. Schedules can target a single test, a directory, or a tag.
See the Schedules page for the full reference.
API
Use the API to start runs programmatically. Both single-test and bulk-run endpoints accept an optional config object with the same shape as the config overrides in the console dialog.
Concurrency and Plan Limits
If all parallels are in use, a run is created with status pending and starts automatically when a parallel frees up. A run whose requested workers count exceeds the plan limit is rejected immediately.
The Concurrency Usage widget in the navbar shows parallels in use in real time.
Following a Run
After a run starts, you are redirected to the run detail page where status updates appear live. From CI, poll the Test Runs API or set up a webhook to be notified when the run completes or fails.