> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/introduction-to-avo-assure.md). # Introduction to Avo Assure Avo Assure is a no-code, AI-driven test automation platform that works with various software types and product implementation tools. It is used for innovative QA testing of business applications, covering a wide range of capabilities, from the visual layer to underlying services, and databases. It supports web, desktop, ERP, mainframes, mobile apps, and a lot more, making testing easier and efficient. This comprehensive test automation solution is designed to help organizations of all sizes to effectively test their business applications. With its robust features, Avo Assure enables teams to create automated tests covering various aspects of their applications, ensuring higher quality and performance. Whether the business operates in finance, healthcare, retail, or any other industry, Avo Assure provides the tools needed to streamline the testing process, reduce manual effort, and accelerate time to market. Avo's platform vision is to revolutionize automation quality and functionality through thorough testing before any application hits the market. This direction of Avo Assure makes testing a positive and interactive experience rather than a challenge. --- # 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.avoautomation.com/avo-assure/introduction-to-avo-assure.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.