The Detailed Test Report provides an in-depth breakdown of an individual test execution. It captures complete request–response data, validation outcomes, and execution logs, helping QA engineers pinpoint the exact cause of test failures or anomalies.
Navigation : #
← Back to High Level Report
Open in New Tab — Opens the test report in a dedicated browser tab for deeper inspection or sharing.
Test Overview : #
| Field | Details |
|---|---|
|
Test Name |
Error Scenario – Missing access key |
|
Endpoint Name |
GET /api/V4/schedules |
|
Test ID |
e9099931-a110-4217-91c1-bb7eb2116563 |
|
Execution Type |
Automated |
|
Environment |
staging |
|
Date & Time |
10/1/2025, 4:09:00 PM |
|
Execution Time |
86ms |
|
Pass Rate |
25% |
|
Status |
❌ FAILED |
Each execution record is automatically timestamped and environment-linked for accurate traceability.
Error Summary : #
No explicit system-level errors were reported, but multiple validation failures indicate API behavior deviating from expectations.
Validation Results : #
The validation results section compares expected vs. actual outcomes for each defined test assertion:
| Validation Type | Expected | Actual | Result |
|---|---|---|---|
|
statusCode |
401 |
200 | ✗ FAILED |
|
responseBody (Type Check) |
string |
object | ✗ FAILED |
|
responseBody (Schema Check) |
string |
object | ✗ FAILED |
|
responseTime |
< 1000ms |
80ms | ✓ PASSED |
Validation Summary :
✓ 1 Passed ✗ 3 Failed #
Failed validations highlight mismatched expectations between the API’s response and the defined schema or behavior rules.
Request & Response Details : #
Request : #
| Property | Details |
|---|---|
|
Method |
GET |
|
URL | |
|
Timeout |
30000ms |
|
Headers |
{ “accessKey”: “123456” } |
|
Body |
– |
|
Params |
– |
Response : #
| Property | Details |
|---|---|
|
Status |
200 OK |
|
Headers |
{ “cache-control”: “no-store, must-revalidate, no-cache”, “pragma”: “no-cache”, “content-length”: “7190”, “content-type”: “application/json; charset=utf-8”, “expires”: “Mon, 01 Jan 0001 00:00:00 GMT”, “server”: “Microsoft-HTTPAPI/2.0” } |
The response was successfully received but returned an unexpected HTTP 200 instead of 401, indicating improper access control handling in the API layer.
Execution Logs : #
Each test generates structured logs to trace execution flow, timing, and debugging details:
[2025-10-01T10:39:00.592Z] [Scheduler] ❌ Test FAILED: 200 (82ms)
[2025-10-01T10:39:00.592Z] [Scheduler] === CREATING TEST RUN RECORD ===
[2025-10-01T10:39:00.597Z] [Scheduler] ✅ TestRun record created: 259a8649-3948-4366-8fc4-de70a6c1cb41
[2025-10-01T10:39:00.599Z] [Scheduler] 🔍 DEBUG – Stored request object
[2025-10-01T10:39:00.599Z] [Scheduler] 🔍 DEBUG – Stored response object
[2025-10-01T10:39:00.599Z] [Scheduler] 🔍 DEBUG – Stored validation results
[2025-10-01T10:39:00.600Z] [Scheduler] 📊 Test Summary: FAILED in 108ms (HTTP: 82ms)
[2025-10-01T10:39:00.600Z] [Scheduler] === TEST 6/6: Error Scenario – Missing access key ===
[2025-10-01T10:39:00.600Z] [Scheduler] Test ID: e9099931-a110-4217-91c1-bb7eb2116563
[2025-10-01T10:39:00.600Z] [Scheduler] Test Name: Error Scenario – Missing access key
[2025-10-01T10:39:00.600Z] [Scheduler] Test Method: GET
Log Highlights : #
- Confirms successful request execution and record creation
- Displays captured request/response objects for debugging
- Records total runtime and validation summary
Purpose : #
The Detailed Test Report is designed to:
- Enable deep inspection of failed or inconsistent test cases
- Provide developers and QA engineers with request-response context
- Trace issues to specific validations or environment behaviors
- Support reproducibility of failures via detailed execution data
Best Practices :
- Review each failed validation with schema definitions before re-executing
- Use timestamps and environment tags to identify configuration mismatches
- Compare response payloads from different environments for consistency
- Archive or export detailed reports for audit and compliance purposes
