Detailed Test Report

Overview

This page describes the Detailed Test Report for Functional runs: one API test case with endpoint-centric evidence (request/response, status code, assertions).

For Workflows runs, the detailed screen uses a different layout (integration summary, node metrics, sequential nodes, unified log). See Detailed Test Report (Workflow).

How you open this screen

1. Test reporting → choose a row with Run type Functional → View report.
2. On the High-level test report, use View report on a test row.

Functional runs do not use Workflow execution details.

Header

• Title Detailed Test Report with back navigation.
• Actions often include copy, open in new window, and download (where enabled).

Test summary

Typical fields include:

• Test name, status (for example Passed/Failed), pass rate (with progress bar)
• Test ID
• Endpoint — HTTP method (badge) and path
• Project, feature
• Execution time, runner (for example Engine), response time
• Status code (actual HTTP status)
• Environment, execution type (for example Manual), date and time
• Priority, run ID

Many values include a copy control next to the field.

Request and response details

Large expandable sections (chevron):

• Request information — request method, timeout, request size, full request URL, request headers (expandable row count)
• Response information — response body, headers, and status-related detail

Use this area to compare what was sent and what came back against your assertions.

Assertions and logs

• Assertion or validation results (expected vs actual) where the product surfaces them for Functional tests.
• Execution or trace logging may appear below or inside expandable panels.

Debugging tip: Start with status code and the first failed assertion, then expand request/response to verify URL, headers, and body.

Related articles

• Detailed Test Report (Workflow) — Workflows run type
• High-level test report
• Test reporting
• Debug Logging