Overview

Detailed Test Report (Workflow) documents the Workflows run type detailed screen in Reporting. It is not the same layout as the Detailed test report used for Functional runs (single API test case, endpoint-centric request/response).

You open this report after Workflow execution details, using View report on a node row. The UI title may still show Detailed Test Report; this article describes the workflow-specific structure.

How you get here

Test reporting → View report on a Workflows execution.
High-level test report → View report on a workflow row.
Workflow execution details → View report on a node row.

Page title Detailed Test Report (product label) with back navigation.
Actions often include copy, open in new window, and download where enabled.

Execution summary (integration / workflow)

Typical fields include:

Integration test name (workflow name)
Status and success rate (with progress bar)
Integration test ID
Project, executed by
Execution time, environment, execution type, date and time, run ID

Copy controls may appear next to individual fields.

Summary metrics (node counts)

Summary cards for the workflow run, for example:

Total nodes
Executed
Passed / Failed / Skipped / Errors

These reflect the whole workflow, not only the node you clicked—even though you arrived from one node row.

Node executions (sequential)

Nodes listed in execution order (for example Start, then each test node).
Each entry: node type (for example Start node, Test node), label (step description or API check), status (Passed/Failed), duration, start time where shown.
Rows are expandable for per-node detail (request/response or validation where the product provides it).

Use this list to see which step failed and how earlier nodes behaved.

Unified execution log

Unified execution log (often collapsed) contains trace output for the entire workflow run, useful when failures span multiple nodes.

Debugging tips

Identify the first failed node in the sequential list.
Expand that node before assuming a later failure is the root cause.
Cross-check environment and auth if a node’s HTTP outcome looks wrong.
Open the unified log when you need ordering and messages across the full run.

Detailed test report — Functional run type (single API test)
Workflow execution details
High-level test report
Test reporting
Debug Logging

Detailed Test Report (Workflow)