Create combined launches

Use a combined launch when your team wants one execution context that mixes manual and automated work for the same delivery scope.

When to use a combined launch

Combined launches are useful when:

• one release decision depends on both manual and automated evidence;
• manual and automated checks should be reviewed together by the same team;
• triage, dashboards, and defect handling should happen in one place instead of across separate launches.

This is the most natural way to keep mixed execution in one visible decision flow instead of treating manual work and CI work as unrelated tracks.

What a combined launch gives you

A combined launch keeps:

• manual test results;
• automated test results;
• launch-level metadata such as tags, links, and environments;
• defects and reruns;
• later comparison and dashboard updates

inside one launch.

That means the team does not need to reconcile two separate launches by hand before it can decide what happened in the run.

How to create one

For the first implementation, use Create a combined launch.

The flow is:

1. Select the manual and automated scope that belongs to the same validation task.
2. Start the run from Allure TestOps.
3. In the run dialog, confirm the correct job for the automated portion and the correct assignees for the manual portion.
4. Submit the run so Allure TestOps creates one launch for both execution modes.

What happens afterward

After the run starts:

• automated results arrive through the configured job run or job runs;
• manual execution progress appears in the same launch;
• the team can triage failures, create defects, rerun the automated subset, and review overall progress without switching to a second launch.

After the launch is closed, the combined result contributes to the same cross-launch history and analytics as any other launch.

When a combined launch is better than separate launches

Prefer a combined launch when the question is shared, for example:

• "Is this release candidate ready?"
• "Did both the manual smoke scope and the automated regression scope pass?"
• "What do we still need to investigate before closing the run?"

Prefer separate launches when the manual and automated work are unrelated, belong to different delivery scopes, or will be reviewed and closed independently.

Next steps

• Launches for lifecycle and review behavior.
• Test plans for reusable mixed scopes.
• Run automated tests for the automated part of the combined flow.