> For the complete documentation index, see [llms.txt](https://docs.walnutai.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.walnutai.ai/reports-and-analytics/reports/test-case-reports/detailed-execution-report.md).
# Detailed Execution Report
* Click on a **Test Run ID** from the Execution Results Table.
* You will be redirected to the **Detailed Execution Report** page for that specific run.
What You See on This Page:
* **Execution Summary Section** – Displays overall run information.
* Test Case Name and ID
* Version and Run count
* Execution Environment
* Executed By
* Execution Date & Time
* Overall Status (Passed / Failed / Pending)
* Total Duration
This section gives a quick overview of the execution result.
* **Multiple Iterations (if applicable)**\
If the test case is executed with multiple iterations (e.g., different test data sets), each iteration is grouped under a single test run in the report.
* The total number of iterations is displayed (e.g., **“5 iterations”**)
* Execution result is shown as a summary (e.g., **5 Passed / 0 Failed**)
* Each iteration runs the same test with different data inputs
* Steps are executed and recorded for each iteration individually
* Helps compare results across different data inputs and identify failures specific to certain iterations
* You can click on the test run to view detailed step-level results for each iteration
* **Step-Level Results Section** – Shows all executed steps in order.
* Step Number
* Status (Passed / Failed)
* Step Description
* Actual Result
* Test Data
* Execution Time
Each step clearly shows what action was performed and what result was received.
* **Step Filters**- You can filter steps using:
* "All"
* "Passed"
* "Failed"
* "Skipped"
This helps you quickly focus on specific step results.
* **View Step Details**
* Click on any step to open its detailed execution view. This provides complete visibility into what happened during that specific step, including:
* Step input values used during execution
* Step output or response received
* Execution time taken for the step
* Screenshot (if captured during execution)
* Status indicator (Passed / Failed)
* When you encounter a failure and want to log a defect, you can click **“Bug”** directly from a failed step, which will automatically create an **Action Item** with the captured error details, step information, and supporting evidence for tracking and resolution.
* The **Detailed Execution Report** gives a clear, step-by-step breakdown of the entire test run, helping you understand the exact behaviour of the application, troubleshoot failures efficiently, and maintain complete execution traceability.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.walnutai.ai/reports-and-analytics/reports/test-case-reports/detailed-execution-report.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.