High-Level Test Report

Overview

The High-Level Test Report is the first screen after you open Test reporting and choose View report on an execution row. It summarizes one run so you can see outcome distribution and drill down.

What you see depends on Run type on the execution (Functional or Workflows).

Common elements (both run types)

Typical metadata cards include:

• execution date and time
• duration
• executed by
• project
• environment
• execution type (for example Manual or Automated)
• Run type (Functional or Workflows)
• pass rate (often with a progress bar)
• test run pack name when applicable

The header usually includes actions such as back navigation, copy, export/open, and download where your deployment supports them.

Functional runs (two-step reporting)

For Functional runs, the high-level page focuses on tests (API test cases), not workflow nodes.

You will typically see:

• Test distribution — for example a chart and legend for passed, failed, error, and total
• Test results summary — counts and percentages for passed, failed, error, and total
• Test execution details (or similar) — a table with one row per test: test name, feature, endpoint, start/end time, duration, response time, status, and View report on each row

Next step: use View report on a test row to open the Detailed test report for that single test. There is no workflow middle step for Functional runs.

Workflow runs (three-step reporting)

For Workflows runs, the high-level page is organized around the workflow pack and workflows, not individual API tests in the same layout as Functional.

Typical sections include:

• Workflow pack execution summary — pack-level metadata (execution time, duration, executed by, test run pack, project, environment, execution type, pass rate)
• Workflow execution summary — aggregated passed / failed / error / total for the workflows in the pack
• Workflow execution details — a table listing each workflow: name, start time, duration, status, node summary (for example how many nodes passed), and View report per row

Next step: use View report on a workflow row to open Workflow execution details. From there you can open Detailed Test Report (Workflow) for a specific node when needed.

Triage tips

1. Confirm Run type so you know whether the next step is straight to a test detail (Functional) or to workflow node detail (Workflows).
2. Use search or filters on the high-level tables if your UI provides them.
3. Start with failed or error rows before expanding scope.

Related articles

• Test reporting
• Workflow execution details
• Detailed test report
• Detailed Test Report (Workflow)