Run Detail

The run detail page is a three-pane command centre with four tabs — Results, Status, Activity, and Issues. It is where testers execute tests, reviewers track progress, and managers monitor quality.

Think of it as mission control

The folder tree on the left is the mission checklist — organised by system or module. The results table in the centre is the status board — every test case lined up with its current outcome. The case details panel on the right is the deep-dive screen — open it to inspect a single case, read its steps, review past results, and record a new one. Four tabs across the top switch between dashboards: live execution (Results), health overview (Status), timeline (Activity), and defect tracker (Issues).

The three-pane layout

Left pane — Folder tree

Shows the folder structure of the test cases included in the run. Click a folder to filter the results table to only cases in that folder. The pane is collapsible — drag to resize or click the toggle to hide it entirely.

Centre pane — Results table

The primary execution workspace. Lists every test case in the run with its current status, assignee, and metadata. Columns are customisable. Click a row to open the case details panel.

Right pane — Case details panel

Opens when you click a case row. Shows the full case information, test steps, result history, and the Add Result button. The panel can be maximised to full width. Use the prev/next buttons to step through cases sequentially.

Results tab

The Results tab is the primary view when you open a run. It shows the folder tree, results table, and case details panel.

Results table columns

The table displays one row per test case. Columns are customisable — drag to reorder, resize by dragging column edges, and toggle visibility from the column settings menu. Preferences are saved per project.

Column preferences are saved per project. Reorder, resize, or hide columns and the layout is remembered next time you open any run in the same project.

Quick status change

Each row has a status dropdown that lets you set the result status without opening the full Add Result modal. This is useful for rapid triage — for example, marking a batch of cases as Blocked.

Sorting and pagination

Click a column header to sort. Sortable columns include: Case ID, Title, Template, Lifecycle State, Estimate, Assigned To, and Updated. The table uses virtualised scrolling and loads 100 cases per page with automatic pagination as you scroll.

Case details panel

Click any row in the results table to open the case details panel on the right.

Case header

The panel header shows the case ID, title, folder path, template name, tags, environment, and estimated time. A navigation bar provides Previous and Next buttons to step through cases in table order.

Test steps

If the test case includes a STEPS field, each step is displayed with its position number, instruction content, and expected result. Steps are read-only in the panel — they show what the tester needs to do.

Custom field values

Template fields attached to the test case are displayed as read-only values below the steps section.

Results sub-tab

A chronological timeline of every result recorded for this case within the run. The most recent result appears at the top. Each entry shows:

• The result status with colour-coded icon
• The user who recorded it, with avatar
• The timestamp
• Elapsed time (if recorded)
• Step-by-step results (if the case has steps) — each step shows its status icon and any note
• The comment (rich text rendered)
• Attached files with download links
• Linked external issues with status badges

Issues sub-tab

External issues linked to any result for this case. Shows the issue source (e.g. Jira), key, title, and current status.

Navigation

Use the Previous and Next buttons at the top of the panel to move through cases in the same order as the results table. The maximise button expands the panel to full width for easier reading.

Status tab

The Status tab is a dashboard summarising the run’s overall health.

• Run metadata — created and updated dates, the assigned cycle with its status badge, the lifecycle state, contributor avatars, and the environment.
• Progress — a completion rate percentage, the number of remaining untested cases, and a visual progress bar.
• Status grid — coloured boxes for each result status showing how many cases have that outcome. An additional box shows the untested count.
• Edit — an Edit button opens the run modal to change metadata.

Activity tab

The Activity tab shows a timeline of test execution grouped by date.

• Each entry records who executed which case, the result status, and the timestamp.
• A summary row per day shows status counts — how many Passed, Failed, Blocked, etc.
• Filters let you narrow the timeline to specific statuses.
• A date range selector controls the visible window.
• Pagination loads older activity entries on demand.

Issues tab

The Issues tab aggregates all external issues linked to results across the entire run. It acts as a defect dashboard — showing issue keys, titles, statuses, and which test cases they are linked to. Use it to get a quick view of all defects found during the run without opening individual cases.