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

# Test Case Reports

The **Test Case Reports** page provides detailed visibility into individual test case executions. It allows you to monitor execution status, review trends, and inspect step-level results.

* **How to Access Test Case Reports** -**Path:** "Reports" → "Execution Reports" → "Test Cases"

  * Click **"Reports"** from the left navigation panel.

  * Click on the **"Test Cases"** tab.

    <figure><img src="/files/0kK5bIuJCJn9n67qwNwl" alt=""><figcaption></figcaption></figure>

  * **What You See on the Test Cases Page**: The **Test Cases** page is divided into three main sections that help you quickly review execution results.
    1. **Filters Section** – Allows you to narrow down execution data.
    2. **Execution Analytics Section** – Provides visual summaries of execution trends and status.
    3. **Execution Results Table** – Displays detailed information for each test run.

  * **Filter Execution Results**: You can use filters to refine the execution data shown on the page.
    * **Date Range** – View executions within a specific time period.
    * **Status** – Filter by Passed, Failed, or other statuses.
    * **Test Case** – View results for a specific test case.
    * **Suite** – View executions linked to a particular suite.

  * **Execution Analytics**: The **Analytics Section** provides visual summaries to help you quickly understand execution performance and stability.
    * Test Execution Trend – Displays pass and fail results over time.
      * **Green** – Passed, **Red** – Failed, **Blue** – Not Executed, helping you quickly identify execution stability and trends across multiple test runs.
    * Test Run Distribution – Shows overall execution breakdown in a donut chart.
      * **Total Runs** – total executions, **Passed** – successfully completed runs, **Failed** – runs with issues, **Not Executed** – runs not completed, providing a quick summary of overall execution health.

  * Click **"Apply"** to update the results.

  * Click **"Reset"** to clear all selected filters.

  <figure><img src="/files/pYWjNHV6sQ0xsXX6Dl4F" alt=""><figcaption></figcaption></figure>

* **Execution Results Table:** The **Execution Results Table** displays detailed information for each test run, allowing you to review execution history in a structured format.

  * **Execution Date** – Shows when the test was executed.
  * **Test Run ID** – Unique identifier generated for each execution.
  * **Test Case ID** – Identifies the associated test case.
  * **Test Case Name** – Name of the executed test case.
  * **Duration** – Total time taken for execution.
  * **Status** – Indicates Passed, Failed, or other execution states.
  * **Executed By** – Displays who triggered the execution.

  <figure><img src="/files/MW7sCHDbX9ckALF8Jpao" alt=""><figcaption></figcaption></figure>


---

# 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.md?ask=<question>&goal=<endgoal>
```

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