> 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-scenarios-management/executing-test-scenarios.md).
# Executing test scenarios
Efficiently run, track, and manage test scenario executions. Use 'Run all' or 'Run selected' to execute cases, view detailed execution history, and control progress in one place.
You can execute either a selection of test cases in your scenario, or the entire scenario. To execute the full scenario, click 'Run all'. The execution window, which you already know from test executions, opens, and you can execute each test case step by step.
Run all command
Test Scenario execution form
To execute a selection of test cases, select the test cases and click 'Run selected'.
Run selected command
Keep tabs on the latest local executions directly within your test scenarios. To access this information, simply click on 'Test Cases'. For a comprehensive overview of recent executions, head over to the 'Executions' tab. This section presents all executions in a clear table format, enabling you to effortlessly manage their progression. Whether you need to continue, abort, finalize, or flag executions as irrelevant, the 'Executions' tab provides a centralized hub for efficient execution management.
Execution tab view
If you want to see even more detail, double-click an execution.
Execution's detail view
---
# 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-scenarios-management/executing-test-scenarios.md?ask=&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.
