> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/items/defects-management/review-found-or-linked-defects-to-the-test-execution.md).

# Review found or linked defects to the test execution

Easily review and manage defects linked to test executions in aqua. View, edit, and track related issues by status to streamline retesting and ensure defect resolution.

In aqua  you have the possibility to check dependent defects found or linked during the execution of a test case. Thus, you can easily check, if the defect is fixed when retesting it.&#x20;

There are multiple ways on how you can do it in aqua.&#x20;

If there are any linked defects as soon as your execution has the status **failed** or **blocked**, the system will promt you to review linked defects.

&#x20; ![](http://aquawiki.andagon.com/pictures/drex_defect_review_in_test_execution_custom.png)&#x20;

When you click to view them, a window will open with an overview of all related defects, grouped by their status.&#x20;

Via  the 'Edit' option you can then open and modify the defect in a separate tab, *e.g. set the status to 'Fix' or add a note with relevant information.*

<figure><img src="http://aquawiki.andagon.com/pictures/drex_defect_review_in_test_execution_custom_2.png" alt=""><figcaption><p>Review defects</p></figcaption></figure>

You can also always review related defects by clicking <img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FoEkuAJcHa5HGbkHkS4ht%2Fimage.png?alt=media&amp;token=abb64739-7022-4710-990e-c3f745d30010" alt="" data-size="original">in the ribbon of the test execution.&#x20;

If there is a defect found during the test run, at the 'Executions' page there will an indicator. When you click on the bug icon, the modal with all connected bugs will be shown.

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2F2qkuAZzpwJF4V5GL4LmX%2Fimage.png?alt=media&amp;token=3b270809-30fa-4f82-bca2-4039ff8d9b82" alt=""><figcaption><p>Test executions page</p></figcaption></figure>

If you open a test execution details page, you'll see which test step has a linked defect and the bottom you'll see all related defects that you cn review and later retest.

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FJcIx6IPfVvFI1sWIuMps%2Fimage.png?alt=media&amp;token=365881bc-3eca-4c02-84dc-cd2d21209548" 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aqua-cloud.io/documentation/items/defects-management/review-found-or-linked-defects-to-the-test-execution.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
