> 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/quick-run-test-execution-of-multiple-test-cases-at-once.md).

# Quick run: test execution of multiple test cases at once

Accelerate QA with aqua's Quick Run - execute multiple test cases at once, customize fields, and streamline defect detection for faster, more efficient software testing.

Quick run of test cases in aqua simplifies the testing process by enabling rapid feedback on software qualit&#x79;**.** This accelerated feedback loop expedites defect identification and resolution, streamlining the development cycle and ultimately delivering a superior end product. Moreover, Quick Run fosters more frequent testing, enabling early detection of issues that could otherwise fester into major problems later in the development process.

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FOTceF8Cyp52V5UkBqOPu%2FQuick%20run.gif?alt=media&amp;token=4b8913ca-830a-4399-8b67-d0d5d757c306" alt=""><figcaption></figcaption></figure>

To quickly run a few test cases at once, first open 'Test case' tab at the navigation page.

Then select the test cases you want to execute, then righ-click and from the menu select 'Quick run'.

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FvbUcXgP5qX7MZoKUlGWk%2Fimage.png?alt=media&amp;token=3267b8ab-c7e7-46f4-bf0c-c9bf84c15fc2" alt=""><figcaption></figcaption></figure>

When modal appears, you will see the list of the selected test cases. Quickly review if you select the right ones.

Select a value set for each test case if you want to parametrise them

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FgePqJAlwwP5BqMGUL1im%2Fimage.png?alt=media&amp;token=806c71d4-2959-442f-aa9a-83c78a6bbb58" alt=""><figcaption></figcaption></figure>

Then select values for each field you added to your test case from the template page.&#x20;

Add labels (optional).

Then define the status and provide a comment in the the actual result section.

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FG5VMtA6NGrAIoC63jdJX%2Fimage.png?alt=media&amp;token=ea24070f-6c36-44e6-b663-a588b21306dd" alt=""><figcaption></figcaption></figure>

Run the execution.

Optionally you can select 'Run and finalize'&#x20;

{% hint style="info" %}
Please note that once you select 'Run and finalize', the runs can't be modified later.
{% endhint %}

When you run the test cases, the status and the actual result are applied to all steps of the test cases  and executions. The results  including details, status and actual results are saved in aqua as in general manual test execution and can be reviewed later under each test case.

**How to define custom fields for Quick run**

Select a project where you store your test cases and then click on the 'burger' menu icon.

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2Fe33wTbhQGFWZflb3U8se%2Fimage.png?alt=media&amp;token=eb12de1d-bcc3-4dfd-9afb-52ac65edbee3" alt=""><figcaption></figcaption></figure>

Click on the 'Template' option

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FRLdO8aO64FEzjPRJN7ND%2Fimage.png?alt=media&amp;token=9c960d56-0d4f-4009-806f-c343fe0d43d6" alt=""><figcaption></figcaption></figure>

At the bottom select the 'Test run configuration' tab.

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2Fo3TWBcbJItAyjeFf7vog%2Fimage.png?alt=media&amp;token=66486519-d37d-4576-935f-3f0251bb61aa" alt=""><figcaption></figcaption></figure>

Then add any field and as many as you need.

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2Fu3y22Inwz2Rb6mzvwsYp%2Fimage.png?alt=media&amp;token=22ed7c2b-d866-4b93-8e6b-1ffa7b5cc43b" alt=""><figcaption></figcaption></figure>

Save the changes and navigate back to the project.

{% hint style="info" %}
Please note that once you define the fields, they are available either you:

* quickly execute test cases from navigation,
* run full manual test case or,
* execute it within a test scenario.
  {% endhint %}


---

# 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/test-cases-management/quick-run-test-execution-of-multiple-test-cases-at-once.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.
