> ## Documentation Index
> Fetch the complete documentation index at: https://docs.docketqa.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Getting started with writing your first test on Docket

### 1. Create a New Test Suite with Tests

* Create a new [test suite](/essentials/test-suite).
* Create a [new test](/essentials/test-creation) and give Docket a testing prompt for a flow you would like to see tested.
* Learn about [AI Steps](/essentials/ai-steps) and [Recorded Steps](/essentials/recorded-steps) to understand how to build effective tests.
* Testing a native iOS or Android app? See the [Mobile Apps](/essentials/mobile-apps) guide for how to upload your first build and point a test at it.

### 2. Add Agent Rules (Optional)

* Help the agent understand app-specific behavior via [agent rules](/essentials/agent-context).

### 3. Run the Test

* [Run the test](/essentials/running-test) manually, schedule it, or build a [CI/CD integration](/essentials/ci-integration).

### 4. Review the Results

* Tests return a clear pass/fail outcome
* If failed, Docket gives a concise reason why—based on real usability criteria

***

💡 **Note**: Docket fails fast. If a real user would be confused, blocked, or slowed down, the test fails by design.

**Next Steps:**

* [Creating a Test](/essentials/test-creation) — Deep dive into test creation
* [AI Steps](/essentials/ai-steps) — Learn about natural language test instructions
* [Recorded Steps](/essentials/recorded-steps) — Understand coordinate-based actions
* [Bulk Create](/essentials/bulk-create) — Import existing test cases from documents
* [Generate Tests](/essentials/generate-tests) — Use AI to generate tests from PRDs and screenshots

Need help? Reach out to our team at [founders@docketqa.com](mailto:founders@docketqa.com).