> For the complete documentation index, see [llms.txt](https://quash.gitbook.io/quash-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://quash.gitbook.io/quash-documentation/getting-started/introduction.md).

# Introduction

### What is Quash

Quash is an AI-powered mobile testing platform that helps you create, run, and maintain automated tests without writing code. Simply describe what you want to test in plain English, and Quash generates the test cases for you.

**Key capabilities:**

* **AI test generation** — Write prompts instead of code to create tests
* **Multi-device testing** — Run tests on physical devices, emulators, or cloud devices
* **Team collaboration** — Share workspaces, tests, and results with your team
* **Automated reporting** — Get detailed execution reports and insights

**Perfect for:** QA teams, mobile developers, and product teams who want faster, more reliable testing without the complexity of traditional automation frameworks.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://quash.gitbook.io/quash-documentation/getting-started/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.