> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-reports-section/read-a-report/viewing-result-summary.md).

# Viewing Result Summary

The Test Report Summary provides a detailed view of test executions, including individual test case details and their execution status.

To view the Test Report Summary, perform the following actions:

1. On the **Home** page, under **Projects**, select the required **Project**.
2. Select **Design Studio** and select the **Reports** page.
3. Select the **Testcase Details** icon <img src="/files/0s7arTPqJpXPSlHXRv1d" alt="" data-size="line">. The **Run Details** tab opens.

<figure><img src="/files/Zh3C2LCfWLKO0fJdRuMi" alt="" width="375"><figcaption></figcaption></figure>

4. Select the **View Reports** icon <img src="/files/pJB4LnIYNl3nnztoW9ze" alt="" data-size="line">. The **Result Summary** tab opens.

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

5. In the **Result Summary** window, you can view the following details:
   * **Test Case Name**: Displays the name of the Testcase being executed.
   * **Project Name**: Indicates the associated project name.
   * **Execution Mode:** Refers to how a Testcase was triggered or initiated.
   * **Start Date/End Date Time**: Specifies the start and end timestamps for the test execution.
   * **Execution Through:** Displays machine name or user details in reports to identify where and who executed the Testcase.
   * **Run Result**: Displays the overall execution result of the test case, such as **Pass**, **Fail**, or **Terminate**.
   * **Time Elapsed**: Displays the total time taken to complete the test execution.
   * **Executed Browser:** Shows the name of the browser on which the Testcase execution was triggered.
   * **Failure Reason**: Displays the reason for the execution failure.
   * **Overall Status:** Reflects the Testcase execution's final outcome.
   * **Progress Bar:** The progress bar visually depicts the percentage of passed, failed, terminated, in-progress, or queued steps.
6. **Expand** the first step arrow from the **#** column to view the detailed analysis of the execution, including all the test step details for the selected test case.

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

7. Explore the corresponding **Test Case** to view the following details:
   * **Run Result:** Displays the overall status of the Test Step Group and the execution result for each Test Steps in different colors.
     * **Green**: Indicates Test cases are passed.
     * **Red**: Indicates Test cases are failed.
     * **Grey**: Indicates Test cases are terminated.
     * **Yellow**: Indicates Test cases are executing (In Progress).
     * **Blue**: Indicates Test cases are in queue for execution.
     * **Orange**: Indicates Test cases are skipped.
   * **Time Elapsed:** Displays the duration taken to execute the test step.
   * **Step Details:** Displays the Test Step Group name along with detailed information about each step performed during execution.
   * **Error Details:** Displays the reason or error message for the failed test step.
   * **Remarks:** Displays additional information or comments related to the execution of the test step.
   * **Time Elapsed:** Displays the time taken for execution
   * **Found By:** Indicates the identifier through which it has been recovered
   * **Defect:** Indicates the option to log a defect in the defect management tool.

{% hint style="info" %}
**Note:** When a test case uses a captured element that is deleted, the execution stops automatically, and the Testcase is marked as Terminated in the Status column of the Reports section, and the Error Details column displays Deleted element found, instead of leaving the Testcase in In Progress.

**Example:**

If a test case contains a captured element like Submit Button and this element is deleted, execution stops immediately. The Status column shows Terminated, and the Error Details column displays element not found.

To learn how to add test step details, [click here](/avo-assure/create-and-execute-tests-with-design-studio/working-with-test-case-section/create-test-case/create-test-step-group/add-step-details.md).
{% endhint %}

8. Select the **Eye** icon <img src="/files/DCle0bvq5YConJC1SQLB" alt="" data-size="line"> from the **Action** column to view the screenshot of the individual element captured from the Application Under Test (AUT).

<figure><img src="/files/WijJ1UjDCGJpym1hgpv3" 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.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-reports-section/read-a-report/viewing-result-summary.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.
