> For the complete documentation index, see [llms.txt](https://docs.qyrus.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qyrus.com/docs/welcome-to-qyrus.md). # Welcome to Qyrus Welcome to Qyrus, a Simple, Smart and Scalable platform for all things Quality. This is a consolidated documentation site for Qyus and you will find documentation for all our services. Please use the grid below to access documentation for your respective service. {% hint style="info" %} Every service opens its own tab so that its easier for bookmarking the page depending on what service you use. {% endhint %} {% hint style="info" %} For any further queries please reach out to {% endhint %}
Cover image
Web TestingWeb testing Service Icon.svgWeb Testing
API TestingAPI testing service icon.svgAPI Testing
Component TestingComponent service icon.svgComponent Testing
Mobile TestingMobile testing service icon.svgMobile Testing
Desktop TestingDesktop-testing-service icon.svgDesktop Testing
API MonitoringAPI monitoring service icon.svgAPI Monitoring
Web PerformanceWeb Performance Service Icon.svgWeb Performance
Service VirtualizationService Virtualization service icons.svgService Virtualization
Device FarmDevice Farm service icon.svgDevice Farm
Data TestingData Testing Service icon 1.pngData Testing
Test OrchestrationTest Orchestration service icon.pngWelcome to Test Orchestration
--- # 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.qyrus.com/docs/welcome-to-qyrus.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.