> 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/test-cases-management/manual-testing.md).

# Manual testing

If a test is specified with test steps and/or test conditions, you are able to manually execute the test case. Open a test case and click on Run.![](http://aquawiki.andagon.com/pictures/drex_running_tests___manual_execution_custom.png)Clicking Run opens an execution configuration window where you can enter the tested version and other fields, configured in the Test run configuration template in the [Project Template](/documentation/project-configuration/old-project-template-configuration-fields.md). \
\
Furthermore, in this form, you can choose the value set, if defined. The value set is described in section [Variable Manager](/documentation/items/test-cases-management/test-data-or-variables-manager.md). Test execution labels can be used to track information about the System under Test and Test Environment. More details [here](/documentation/items/test-cases-management/test-environment-tracking-with-labels-tags.md). <br>

<figure><img src="/files/cx47OK3ZGuw8QnAuZxDx" alt=""><figcaption><p>Run configuration window</p></figcaption></figure>

A new tab shows step-by-step the tasks to be performed in the given test case. The screenshot below shows a conditional step. The Actual Results field is used to document the current behaviour. As with all description fields, the text can be formatted and tables or images can be added (using the toolbar at the bottom of the results field or by copy & paste).

&#x20;&#x20;

<figure><img src="/files/dNg3iVkBOaSzImOUV7OL" alt=""><figcaption><p>Execution form</p></figcaption></figure>

If the first step is passed, we confirm the result by clicking on the Pass button. The first step will be green, and the next step will be displayed automatically.

<figure><img src="/files/EzTlCWsLOj2QjYlgmkHV" alt=""><figcaption><p>Marking the Test Case steps outcome</p></figcaption></figure>

The second step is a Test Step. Here we find an Instruction and an Expected Result, as well as the Actual Results field. Again, you are going to document your result in the Actual Results field and set the appropriate status. \
\
You can then go through all the individual test steps and mark them as&#x20;

* Pass,&#x20;
* Fail,&#x20;
* Blocked,&#x20;
* Not Applicable.&#x20;

If you have configured the Actual Result to be a required field in the [Project Settings](/documentation/project-configuration/additional-project-settings.md), you cannot set an execution status for the steps until this field is empty. When you set a test step to Pass, you automatically proceed to the next step. You can also use the list of steps on the left or the ribbon button to navigate between the steps.&#x20;

Under Add Attachment, you can attach one or more files to this execution. These can be Word files, Excel lists, screenshots, or even zip files containing many screenshots.\
With Take Screenshot  ![](http://aquawiki.andagon.com/pictures/drex_running_tests___manual_execution_custom_5.png)  you can capture your screen or application and edit the screenshot, add comments and insert it into the description field or as an attachment. For more information, see the [Take Screenshot](/documentation/items/general-item-capabilities/take-screenshots.md) chapter. &#x20;

The Save button allows you to save your execution at any time. As long as you have not marked all steps as Pass or at least one step as Fail or Blocked, you can only `Suspend, Save & Close`, i.e. pause the execution. A paused execution can be resumed later in the [Execution ](/documentation/items/test-cases-management/test-execution-results.md)tab of the test case. Once an execution has been executed completely, you can `Finalize, Save & Close` it to save the result in a final and audit-proof way or only `Save & Close` if you want to edit the execution later.&#x20;

All executions including the execution details can then be viewed in the [Execution](/documentation/items/test-cases-management/test-execution-results.md) tab where they can be continued, edited or finalized. If you discover a defect during your execution, you can set the corresponding step to fail and then [create a new defect directly from the execution](/documentation/items/defects-management/creating-a-defect-from-a-test-execution.md) or link an existing defect to this execution. If you successfully execute a test case that is linked to a defect, you can [review the related defects ](/documentation/items/defects-management/review-found-or-linked-defects-to-the-test-execution.md)from the execution and set it to closed, for example.

<figure><img src="/files/78BP1ifrxKFrBC64mbyU" alt=""><figcaption><p>Saving the completed execution</p></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.aqua-cloud.io/documentation/items/test-cases-management/manual-testing.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.
