> 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/aqua-intelligence/create-test-cases-in-seconds-with-aqua-intelligence/create-test-cases-from-the-navigation-page.md).
# Create test cases from the navigation page
Generate test cases instantly from your navigation page using aqua Intelligence. Streamline QA by converting requirements or context into actionable tests in seconds.
When on the navigation page, click on the "+ Add new" button located at the top left of your screen.
Once you select the create "Test case with aqua Intelligence" option, the modal will appear.
In the ‘Context’ field, provide details about the product, feature, or functionality under test. Include any special glossary terms the AI should consider.
Alternatively, you can select a requirement which AI should cover with test cases.
{% hint style="info" %}
However, despite having provided the requirement, you can still include context as additional information. This helps the aqua Intelligence generate more relevant and precise test cases.
{% endhint %}
As soon as the requirement is selected and context provided, choose whether you want to create a single test case or multiple test cases by selecting either ‘One’ or ‘Multiple’ under ‘Number of test cases’.
Use the dropdown menu under ‘Max number of test steps’ to set a limit on the number of steps the test case should include. Options range from 3 to 12 steps or you can select ‘Any’ for no limit.
In cases when you need to create only one test case, you can choose the path (case) which test case should cover: positive or negative.
When you create multiple test cases, aqua Intelligence will generate both: positive and negative path test cases.
As soon as all options are preselected, click the button ‘Create’. aqua Intelligence will analyze a linked requirement or context and start creating test case or test cases.
### **Adding single test case**
When a single test case is generated, you can either regenerate it or add it if you are satisfied with the result.
The generated test case will be linked as a dependent item that covers your requirement.
### **Adding multiple test cases**
When you set aqua Intelligence to generate multiple test cases, once they are ready, you will see the number it created in the corresponding block.
You can switch between the test cases to review them before adding as coverage to your requirement
By default, all test cases will be linked to a requirement as soon as you click the ‘Add button’, but if you see that some of the test cases are not relevant, you can exclude them by unchecking the ‘keep’ icon.
Even when generating multiple test cases, upon saving, all test cases will be added as dependencies if they are generated based on the requirement.
---
# 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/aqua-intelligence/create-test-cases-in-seconds-with-aqua-intelligence/create-test-cases-from-the-navigation-page.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.
