> 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/test-it-easy-way-to-start-run.md).
# Test it: easy way to start run
Easily launch and manage your first test case in aqua. Step-by-step guide to start test executions quickly and efficiently. Ideal for seamless QA onboarding.
The Test It! feature allows you to instantly test items with related test cases or scenarios. To do so, open an item, e.g. a requirement, with related test cases or test scenarios. Click on the button on the ribbon.
If no test case or scenario is specified, a new window opens and you can define and execute a new test case. If only one test case or scenario is associated, the test execution will start immediately. When more than one Test Case or Test Scenario is related to the given element, a window opens where you can select and execute a related Test Case or Test Scenario.
When clicking 'Execute' you will [execute ](/documentation/items/test-cases-management/manual-testing.md)the selected test case or scenario.
---
# 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/test-it-easy-way-to-start-run.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.
