> 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/generate-test-case-based-on-a-file.md).
# Generate test case based on a file
Effortlessly generate precise test cases from your files using aqua Intelligence. Streamline QA workflow with intelligent automation tailored for your project's needs.
In situations when you have your requirements passed to you in pdf, excel or just screenshots of the app as png, or UML diagram for the login process, now you can feed this information to AI and ask it to create a test case based on this information.
Click the ‘Add test case' button on the main page
Then select creation of a test case based on a file.
Upload a file in one of the supported formats
Once the file is uploaded, you can optionally add a description to give aqua Intelligence some context.
Then select the number of steps and path and click the ‘Create’ button.
The aqua Intelligence will start generating a test case.
Once it’s created, save it, review it further, and make any necessary modifications based on specific needs.
Have feedback? Don't hestitate to share! Email us at **** or ****
---
# 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/generate-test-case-based-on-a-file.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.
