> 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/suites-reports.md).

# Suites Reports

The **Suite Reports** page provides visibility into test suite executions. It allows you to monitor execution results and review the test cases executed within each suite.

* **How to Access Suite Reports Path:** **Reports → Execution Reports → Suites**

  * Click **Reports** from the left navigation panel.
  * Click on the **Suites** tab.

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

**What You See on the Suites Page:**\
The Suites page is divided into two main sections that help you review suite execution results.

* **Test Suites Section** – Displays the list of available test suites along with their execution summaries.
* **Execution Results Table** – Shows detailed execution results for the selected suite.

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

**Test Suites Section:** The Test Suites panel lists all available suites.

For each suite you can see:

* **Suite Name** – Name of the test suite.
* **Run Count** – Number of times the suite has been executed.
* **Pass / Fail Count** – Number of test cases passed or failed within the suite.

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

* Click on a suite to view its execution history.
* **Execution Results Table:** The Execution Results Table displays detailed information for each test execution within the selected suite.
  * **Executed At** – Shows when the test case was executed.
  * **Test Run ID** – Unique identifier generated for the 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 or Failed.
  * **Executed By** – Displays who triggered the execution.

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

**Multiple Iterations in Suite Execution -**&#x49;f a test case within a suite is executed with multiple iterations (using different test data), the execution results are grouped under a single test run in the Execution Results Table.

For such executions, you will see:

* **Iteration Count** – Displays the number of iterations executed (e.g., *“2 iterations”*) below the Test Case Name
* **Execution Summary** – Shows a combined result for all iterations (e.g., *2 Passed / 0 Failed*)
* **Single Test Run Entry** – All iterations are grouped under one Test Run ID instead of separate rows
* **Consistent Test Case Execution** – The same test case is executed multiple times with different data inputs
* **Clear Result Visibility** – Helps quickly understand overall success/failure across all iterations

You can click on the **Test Run ID** to navigate to the Detailed Execution Report, where each iteration and its step-level execution can be reviewed individually.

<figure><img src="/files/UQ1GNRwiGb4RSfmgICHI" 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:

```
GET https://docs.walnutai.ai/reports-and-analytics/reports/suites-reports.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.