Subchapter 73.2

Multi Configuration Runs

references/multi-configuration-runs.mdMarkdown2 KBView on GitHub

Read this before creating or reviewing any spec that carries a config_id. These runs need a manual Testmo UI pass after the script finishes, and the pass is mandatory.

Some platforms ship several same-named runs distinguished only by Testmo Configuration (for example one Mobile run per OS). Each variant is its own spec file with the same run_name and a different config_id. Look config ids up via GET /projects/{id}/configs.

Testmo’s /cases API cannot filter by configuration and exposes no per-case config assignment, so these are always two-step runs:

Step 1 (the script): create the run with the spec’s case set and config_id.
Step 2 (manual, Testmo UI): remove the cases that belong to the other configurations. Each spec documents its own step 2 in _comment.

Until step 2 is done the run holds the wrong case set. The script lists every affected run under ; pass that list on to the user.

Read this before creating or reviewing any spec that carries a config_id. These runs need a manual Testmo UI pass after the script finishes, and the pass is mandatory.

Testmo’s /cases API cannot filter by configuration and exposes no per-case config assignment, so these are always two-step runs:

Step 1 (the script): create the run with the spec’s case set and config_id.
Step 2 (manual, Testmo UI): remove the cases that belong to the other configurations. Each spec documents its own step 2 in _comment.

Until step 2 is done the run holds the wrong case set. The script lists every affected run under ; pass that list on to the user.