Selective execution

Run a subset of your test cases — manual, automated, or a mix — from one place. Sulu reconciles everything into a single launch, no matter how the results arrive.

Start a run

You launch a selection from two surfaces:

• Test cases — select cases in the tree, click Run in the bulk-actions bar.
• Test plans — open a plan, click Run launch.

Either way the Run dialog opens. The tabs you see depend on what you selected:

• An all-manual selection shows Launch and Assign.
• A selection with any automated case adds Job and Environment — automated cases need a CI pipeline to actually execute.

How the mode is decided

The selection drives the run mode — you don't pick it.

• All manual → Sulu creates the launch immediately and drops you on the detail page. You check results off by hand.
• Any automated → you must pick a Job first. Until you do, a banner blocks the run. Once a job is chosen, Sulu creates the launch and dispatches the pipeline.

A mixed selection (some manual, some automated) behaves like the automated case: it needs a job, and both kinds of cases land in the same launch.

One launch, many sources

When the launch is created, Sulu seeds a result for every selected case up front — manual and automated alike. The launch shows the full scope from the first second, even before any automation has run.

As automated results stream in from your reporter, they claim the matching seeded results instead of adding new rows. A case you selected, ran in CI, and reported on appears exactly once — never duplicated.

The manual cases keep their seeded results until you triage them by hand. See Manual triage.

TIP

This is why a mixed run is a single coherent launch: the seeded results are the shared anchor that streamed automation and manual triage both write into.

What CI receives

When a run dispatches a job, Sulu sends only the automated subset of your selection to the pipeline, as a comma-separated list of test identifiers in the SULU_TEST_FILTER environment variable:

SULU_TEST_FILTER=PET-37,PET-41,PET-58

Your reporter reads SULU_TEST_FILTER and runs only those tests — see Jobs for how a job forwards it. Manual cases are deliberately excluded from the filter: they have nothing to run in CI and stay queued for a human to triage.

Related

• Run a launch (manual) — the simplest all-manual flow.
• Promote results to Test Cases — turn ad-hoc launch results into first-class test cases.
• Jobs — connect a project to a CI pipeline so automated cases can run.