Product documentationUpdated October 8, 2025
Detailed Test Report
Use the Detailed Test Report to debug a single test—full request/response, assertion outcomes, timing, and execution logs to pinpoint root cause.
Overview
The Detailed Test Report is the evidence view for a single executed test. Use it to pinpoint root cause by inspecting exactly what was sent, what came back, and which validations failed.
What you’ll typically see
- Run metadata: environment, timestamps, executor, configuration profile.
- Validation results: each assertion’s expected vs actual.
- Request details: URL, headers, params, and body.
- Response details: status code, headers, and payload.
- Execution logs: timing, retries (if any), and internal trace lines.
How to debug efficiently
- Start with the first failed validation (it often explains the rest).
- If status code is wrong, check auth and environment config first.
- If schema validation fails, compare the response payload to the contract.
- Re-run a small scope to reproduce consistently.
Related articles
Related articles
- High Level Test Report · Product documentation
- Report – Real-Time Execution Insights · Product documentation
Next steps
- Getting started · Install + connect your spec
- Configuration fundamentals · Stabilize runs
- Initial configuration · Users, licensing, projects
- Release notes · Updates and fixes
Still stuck?
Tell us what you’re trying to accomplish and we’ll point you to the right setup—installation, auth, or CI/CD wiring.