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

# Test Scenarios

- [Test Scenarios](https://docs.aqua-cloud.io/documentation/desktop-client/test-scenarios/test-scenarios.md): Explore detailed test scenario documentation for the Desktop client. Review examples, validation steps, and guidance to streamline your testing process and ensure software quality.
- [Scheduled Executions of Test Scenarios](https://docs.aqua-cloud.io/documentation/desktop-client/test-scenarios/scheduled-executions-of-test-scenarios.md): Schedule and automate test scenario executions in the desktop client. Optimize workflows with detailed steps for configuring and managing recurring test runs.
- [Run Dependency](https://docs.aqua-cloud.io/documentation/desktop-client/test-scenarios/run-dependency.md): Easily manage and configure test scenario run dependencies in the desktop client. Optimize your workflows by setting precise execution order and conditions.


---

# 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/desktop-client/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.