> 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/test-scenarios.md).

# Test scenarios

With test scenarios, test cases can be grouped for a specific execution purpose and executed from within the scenario. An alternative terminology for test scenario could also be test plan or test set. 

The test cases inside the test scenario are not copied or moved, but only referenced, which means the current version of the test cases is always used when executing the scenario. You can therefore add the same test case to different test scenarios and the test case will have an individual execution status within each scenario. The execution list within the test case will still show all executions, whether they where executed from the within test scenarios or directly from within the test case itself. 

:hourglass:Scenarios provide the ability to schedule executions, specify information about the scheduled execution, and easily evaluate the execution status of test cases in different execution contexts.

For example, test cases can be executed for a specific release or software version, for a test environment or test object, or for a specific test phase such as regression, and can be repeated as often as required. You can also define the execution order of test cases, set execution dependencies, specify value sets and automation agents, or assign testers in the context of the scenario. 

To create a new test scenario, click the `New`button in the navigation pane. A new tab opens where you can specify the new test scenario. The user interface consists of the following sections:

<figure><img src="/files/IUQvVbh2VeGegAJP9FKV" alt=""><figcaption><p>Test Scenario view</p></figcaption></figure>

1. Ribbon Bar
2. Properties of the test scenario&#x20;
3. Description
4. Navigation Bar
5. Path

&#x20;


---

# 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-scenarios-management/test-scenarios.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.