Launch detail page

Four URL-driven tabs, plus the header and bulk triage.

Overview tab

A 2x2 card grid:

• Pie chart of test results — clickable slices filter the Tree tab by status.
• Unresolved results — the launch's FAILED and BROKEN results.
• Variables — env vars / tags / build number set by the reporter or run dialog.
• Defects — count of defects linked to results in this launch.

Counts come from the launch's stored metrics — the same source the launches list reads — so the Overview and the list always agree as results stream in.

Tree tab

The launch's TestResults grouped by the active attribute tree.

• Resizable left/right split.
• Manual / Auto segmented toggle.
• Status-chip filter (driven from pie clicks or set directly).
• Right pane: result detail (status, duration, scenario steps, attachments, defect links, assignee).

Defects tab

A read-only table of the defects linked to results in this launch, each with a Jira-status refresh and a jump to the affected result. From the same tab you can link or create a defect for an unresolved failure; the defects themselves are edited on the Defects page.

Logs tab

The launch's full log stream — run-level output and per-test logs — in one chronological panel. A running launch streams new lines live (with a LIVE pill); a finished or closed launch shows the static snapshot.

Header

• Launch name + execution-state badge + LIVE pill (when streaming).
• Tags chips, env-vars badge with popover, default-assignees avatars.
• A prominent red Close launch button (visible, not hidden in a kebab — destructive operations should be plainly visible).
• Promote to Test Cases — turn this launch's automation results into managed test cases (see below).
• A segmented progress bar with per-status counts.

Promote results to Test Cases

Available to editors once the launch is no longer IN_PROGRESS. Click Promote to Test Cases in the header to open a preview → confirm dialog that, for each result, will create a new test case, update an automation-owned case's scenario, or skip a hand-authored manual case (unless you tick it to convert it to automation). Results with nothing to add are summarized as skipped. Confirming writes the cases as new scenario versions — the same path your automated runs use to keep scenarios in sync.

Bulk triage

The Tree tab's bulk-actions bar exposes Pass / Fail / Skip across N selected results. The launch metrics and tree refresh as updates stream back over WebSocket.