> 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.

<figure><img src="https://295337183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9aroNmDWVJAmMjkdy0hx%2Fuploads%2FBkVQbSQzylbGO09YcASc%2Fimage.png?alt=media&amp;token=af48b5db-7e6a-4c7b-b7a8-812d089e8b87" alt=""><figcaption></figcaption></figure>

What You See on This Page:&#x20;

* **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

  <figure><img src="https://295337183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9aroNmDWVJAmMjkdy0hx%2Fuploads%2FqCo8c6TLKy0dNiB06q2m%2Fimage.png?alt=media&amp;token=0e2ca1ad-4518-4825-b5cb-6e9d2b5788c6" alt=""><figcaption></figcaption></figure>

* **Step-Level Results Section** – Shows all executed steps in order.
  * Step Number
  * Status (Passed / Failed)
  * Step Description
  * Actual Result
  * Test Data
  * Execution Time

&#x20;     Each step clearly shows what action was performed and what result was received.

* **Step Filters**- You can filter steps using:
  * "All"
  * "Passed"
  * "Failed"
  * "Skipped"

&#x20;      This helps you quickly focus on specific step results.

<figure><img src="https://295337183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9aroNmDWVJAmMjkdy0hx%2Fuploads%2FJknx2t6xJ7TDZKRZDktX%2Fimage.png?alt=media&amp;token=9ef6baee-39dd-4b51-a278-0f79ffdbc503" alt=""><figcaption></figcaption></figure>

* **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)

  <figure><img src="https://295337183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9aroNmDWVJAmMjkdy0hx%2Fuploads%2FRmz4w8qrXVzlr9GX1bxl%2Fimage.png?alt=media&amp;token=87f9e92d-f0e2-4445-b795-48bab65fab98" alt=""><figcaption></figcaption></figure>
* 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.

<figure><img src="https://295337183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9aroNmDWVJAmMjkdy0hx%2Fuploads%2Fe1VhjWezXnwo6zHWI5R0%2Fimage.png?alt=media&amp;token=88d537b7-4ad3-43a7-b8ec-f01e1b04c011" alt=""><figcaption></figcaption></figure>

* 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.