# Quash Documentation

- [Introduction](https://quashbugs.com/docs/index.md): Quash is an AI-powered mobile testing platform that helps you create, run, and maintain automated tests without writing code.
- [Quickstart Guide](https://quashbugs.com/docs/getting-started/quickstart-guide.md): Hands-on walkthrough: install, connect a device, add an app, run a task, and read your first report.
- [Platform Overview](https://quashbugs.com/docs/getting-started/platform-overview.md): A tour of Quash's layout—sidebar, workspace, slide-in panels—and how teams typically move through it.
- [Core Concepts](https://quashbugs.com/docs/getting-started/core-concepts/index.md): How context compounds in Quash and which core concept page to read before deep Test Studio work.
- [Memory](https://quashbugs.com/docs/getting-started/core-concepts/memory.md): The three memory layers that shape test quality, how they stack, and what happens near token limits.
- [Guidance](https://quashbugs.com/docs/getting-started/core-concepts/guidance.md): How Guidance accumulates from real runs, matures across sessions, and when to audit it in Knowledge.
- [Megumi & Mahoraga](https://quashbugs.com/docs/getting-started/core-concepts/megumi-and-mahoraga.md): Megumi generates tests from context; Mahoraga runs them on device—here is how they split responsibilities.
- [Tokens & /compact](https://quashbugs.com/docs/getting-started/core-concepts/tokens-and-compact.md): Why recipe sessions cap around 200k tokens, how auto-compact works, and when to trigger /compact early.
- [FAQs](https://quashbugs.com/docs/getting-started/faqs.md): Quash is an AI-powered mobile testing platform. Describe what you want to test in plain English — Quash generates the test cases, runs them on real or virtual devices, and returns detailed reports ...
- [Overview](https://quashbugs.com/docs/devices/overview.md): To run tests in Quash, you need to connect at least one device. Quash supports three types of devices, each with different setup requirements and use cases.
- [Physical Android Devices](https://quashbugs.com/docs/devices/physical-android-devices.md): Pair a physical Android device with Quash over USB after enabling developer and debugging options.
- [Physical iOS Devices](https://quashbugs.com/docs/devices/physical-ios-devices.md): Connecting a physical iPhone to Quash involves two stages: registering your device with Apple, and connecting it in Quash. Before you begin, make sure the following prerequisites are in place. Pre...
- [Local Emulators](https://quashbugs.com/docs/devices/local-emulators.md): Connect a local Android emulator in Android Studio, then pair it with Quash to run tasks.
- [iOS Simulators (Mac only)](https://quashbugs.com/docs/devices/ios-simulators-mac-only.md): Run Quash tests on the iOS Simulator from your Mac using Xcode and the Devices panel.
- [Cloud Device](https://quashbugs.com/docs/devices/cloud-device.md): Quash also lets you run tests on real Android devices hosted in the Quash cloud. This is useful if you don’t want to set up local devices or emulators.
- [Device Configuration](https://quashbugs.com/docs/devices/device-configuration.md): Mahoraga is the execution agent that runs on your Android device or emulator. It detects UI elements, executes test actions, captures screenshots, and reports results back to Quash. This page cover...
- [Adding an App](https://quashbugs.com/docs/apps/adding-an-app.md): Register apps and open a five-tab workspace so Recipe understands, authenticates, and tests consistently across sessions.
- [Apps Manager](https://quashbugs.com/docs/apps/apps-manager/index.md): View your apps as cards in one dashboard, then drill into each app's Overview, Builds, and Knowledge tabs.
- [Overview](https://quashbugs.com/docs/apps/apps-manager/overview.md): Confirm identity and package or bundle IDs here—the agent binds Guidance and platform builds to these fields.
- [Builds](https://quashbugs.com/docs/apps/apps-manager/builds.md): Ship binaries to devices with version labels and env tags, and reinstall any past build from history when needed.
- [Knowledge](https://quashbugs.com/docs/apps/apps-manager/knowledge.md): Wire up Guidance memory and optional GitHub so tests mirror real endpoints, models, and your app's quirks.
- [Credentials](https://quashbugs.com/docs/apps/credentials.md): Centralize test accounts and tokens so authenticated flows run without embedding secrets in prompts or tasks.
- [Test Data (In App)](https://quashbugs.com/docs/apps/test-data-in-app.md): The Test Data tab inside an app does not manage test data directly — it shows the datasets linked to this app and provides a direct link to the main Test Data section where you can create and edit ...
- [Overview](https://quashbugs.com/docs/test-studio/overview.md): Turn plain-English feature descriptions into structured, runnable test cases without scripts, selectors, or framework setup.
- [Recipe](https://quashbugs.com/docs/test-studio/recipe/index.md): One persistent Test Studio session holds the full Megumi conversation, settings, context, and every test generated for a feature or flow.
- [Attaching Context](https://quashbugs.com/docs/test-studio/recipe/attaching-context.md): Wire up app, repo, designs, tickets, and docs first so Recipe outputs steps tied to your real UI, APIs, and acceptance criteria.
- [Configuration in Test Studio](https://quashbugs.com/docs/test-studio/configuration-in-test-studio.md): Use CONFIG to steer coverage depth, test scope, platform, priorities, validations, and step verbosity before Megumi responds.
- [Token Management](https://quashbugs.com/docs/test-studio/token-management.md): Learn how session token budgets work, when conversations get heavy, and how /compact keeps long recipes usable.
- [Saving Generated Tests](https://quashbugs.com/docs/test-studio/saving-generated-tests.md): Decide whether generated tests land in the central library or go straight into a suite, and when each path is the right call.
- [Collaboration as a Team](https://quashbugs.com/docs/test-studio/collaboration-as-a-team.md): Combine PRDs, Figma, branches, and Jira in one shared recipe so every role feeds Megumi without writing cases by hand.
- [Test Case](https://quashbugs.com/docs/test-management/test-case/index.md): A test case is a saved, reusable testing instruction. It defines what Mahoraga should do and what a successful outcome looks like — stored in your library so it can be run repeatedly, added to mult...
- [About the Test Cases Library](https://quashbugs.com/docs/test-management/test-case/about-the-test-cases-library.md): The Test Cases library is the central repository for all your test cases in Quash. Every test case your team creates — whether generated by Megumi in Test Studio, or written manually — lives here a...
- [Creating a Test Case](https://quashbugs.com/docs/test-management/test-case/creating-a-test-case.md): Add test cases via the library form for full field control, or generate and save batches from Test Studio when you need many at once.
- [Managing Test Cases](https://quashbugs.com/docs/test-management/test-case/managing-test-cases.md): Click any test case in the library list to open its detail panel. Every field is editable directly — click into any field and make your change. There is no Save button; changes are saved immediately.
- [Best Practices](https://quashbugs.com/docs/test-management/test-case/best-practices.md): Mahoraga reads your instruction and executes it step by step, exactly as written. It does not infer what you meant — it follows what you said. Write instructions the way you would brief a new team ...
- [Test Data Overview](https://quashbugs.com/docs/test-management/test-data-overview/index.md): Separate test logic from inputs: define datasets once and reference them with slugs so one task can run across every row automatically.
- [Creating Datasets](https://quashbugs.com/docs/test-management/test-data-overview/creating-datasets.md): Create named input tables in the editor or import files, with slugs and columns Megumi and Mahoraga use on each run.
- [Importing from File](https://quashbugs.com/docs/test-management/test-data-overview/importing-from-file.md): Upload CSV or JSON to turn existing spreadsheets into datasets: headers become columns and each row is ready for prompt-driven runs.
- [Overview](https://quashbugs.com/docs/prompting/index.md): Central guide for writing high-quality prompts across test generation, task execution, test data, and backend validations.
- [Prompting for Test Generation](https://quashbugs.com/docs/test-studio/prompting-guide-test-generation/index.md): Write high-signal prompts for Megumi so generated tests are specific, complete, and aligned to your real product behavior.
- [Writing Effective Prompts](https://quashbugs.com/docs/test-studio/prompting-guide-test-generation/writing-effective-prompts.md): Translate outcomes into assertions, direct multi-source context, ask strategic questions, refine in place, and structure big prompts.
- [Prompt Playbooks](https://quashbugs.com/docs/test-studio/prompting-guide-test-generation/prompt-patterns-and-examples.md): Five copy-and-adapt patterns for features, user journeys, edge cases, attached specs, and multi-source generation in Recipe.
- [Troubleshooting Prompts](https://quashbugs.com/docs/test-studio/prompting-guide-test-generation/common-mistakes.md): Avoid the usual prompt pitfalls that yield shallow or unexecutable tests, with a direct fix for each pattern.
- [Prompting for Task Execution](https://quashbugs.com/docs/running-tests/task-overview/prompting-guide-task-execution.md): Write clear, executable task prompts for Mahoraga with strong structure, flow control, and reliable verification.
- [Using Test Data in Prompts](https://quashbugs.com/docs/test-management/test-data-overview/using-slug-in-prompts.md): Insert slugs in task and recipe prompts so each dataset row drives its own run, with clear placement and optional multi-dataset combinations.
- [Using Backend Validations in Prompts](https://quashbugs.com/docs/running-tests/backend-validations/using-slug-in-prompts.md): Trigger prompt-action validations mid-flow: where to place the slug, how runs pause UI work, parameters, and how reports treat optional vs required.
- [Task Overview](https://quashbugs.com/docs/running-tests/task-overview/index.md): A task is the most direct interaction you can have with Quash. Write a plain English instruction, select a device, and Mahoraga executes it immediately. No test library to manage, no suite to confi...
- [Creating and Running a Task](https://quashbugs.com/docs/running-tests/task-overview/creating-and-running-a-task.md): Ship ad-hoc UI checks fast: plain-English prompt, model and device pick, execution report—no suite or library setup.
- [Rerun](https://quashbugs.com/docs/running-tests/task-overview/rerun.md): After a successful first run, Mahoraga replays a stored path for speed—unless the UI drifts; then it reasons again and updates what it learned.
- [Suites Overview](https://quashbugs.com/docs/running-tests/suites-overview/index.md): A test suite is a named collection of test cases that run together as a unit. Instead of running tests one at a time, suites let you execute everything related to a feature, a flow, or a release cy...
- [Creating a Suite](https://quashbugs.com/docs/running-tests/suites-overview/creating-a-suite.md): Create a suite end to end: add library or on-the-spot cases, optional groups, pick Sequential or Isolated, run, then extend or retire it.
- [Sequential vs. Isolated](https://quashbugs.com/docs/running-tests/suites-overview/sequential-vs.-isolated.md): Sequential chains state on one device; Isolated resets between cases and can fan out across devices—pick the mode that matches dependencies.
- [Backend Validations](https://quashbugs.com/docs/running-tests/backend-validations/index.md): Pair UI steps with API assertions in the same run: wire a connection, reuse saved checks or prompt-time actions, and combine assertion types.
- [Connections](https://quashbugs.com/docs/running-tests/backend-validations/connections.md): Store base URL, auth, and shared headers once; every validation inherits them so teams stop duplicating credentials and environment details.
- [Creating a Validation](https://quashbugs.com/docs/running-tests/backend-validations/creating-a-validation.md): From wizard fields to required flags: shape one API check atop a connection, tune timeouts and retries, and expose a slug for prompts.
- [Report Dashboard](https://quashbugs.com/docs/execution-reports/report-dashboard.md): Browse execution history, filter by task or suite, and open any run from the Reports hub.
- [Reading an Execution Report](https://quashbugs.com/docs/execution-reports/reading-an-execution-report.md): Clicking a report opens the full detail view, which includes:
- [Sharing and Downloading Reports](https://quashbugs.com/docs/execution-reports/sharing-and-downloading-reports.md)
- [Overview](https://quashbugs.com/docs/integrations/overview.md): Integrations connect Quash to the tools your team already works in. Once set up, Quash can notify your Slack channels when tests fail, automatically create Jira issues from failures, sync with Noti...
- [Slack](https://quashbugs.com/docs/integrations/slack.md): Once connected, the Quash bot posts a welcome message in the selected channel confirming the integration is live.
- [Jira](https://quashbugs.com/docs/integrations/jira.md): Connect Jira to auto-file failures and pull tickets into Test Studio as recipe context.
- [Notion](https://quashbugs.com/docs/integrations/notion.md): Authorize Notion from Integrations to sync documentation and reporting with your workspace.
- [Quash MCP](https://quashbugs.com/docs/quash-mcp/overview.md): Connect Quash mobile-app automation to your AI agent and run tests without leaving your editor.
- [Organization & Members](https://quashbugs.com/docs/reference/organization-and-members.md): Control profile, org details, concurrency limits, invites, and roles from Profile.
- [How Quash Pricing Works](https://quashbugs.com/docs/administration/how-quash-pricing-works.md): Plans, executions, what counts against your usage, and what changes when you upgrade.
- [Troubleshooting](https://quashbugs.com/docs/reference/troubleshooting/index.md): Quick index of setup, run, and Test Studio issues—jump to the page that matches your symptom.
- [Device & Connection Issues](https://quashbugs.com/docs/reference/troubleshooting/device-and-connection-issues.md): Step-by-step fixes for device discovery, Mahoraga setup, WDA, emulators, and cloud queues.
- [Test Execution Failures](https://quashbugs.com/docs/reference/troubleshooting/test-execution-failures.md): Diagnose Partial Success, flaky runs, CI mismatches, credentials, and empty reports.
- [Test Studio Issues](https://quashbugs.com/docs/reference/troubleshooting/test-studio-issues.md): Fix generic tests, lost recipe context, panel updates, and duplicate cases in Test Studio.
- [Glossary](https://quashbugs.com/docs/reference/glossary.md): An AI-powered automation module that performs a specific role in the testing workflow. Quash has two agents: Megumi (test generation) and Mahoraga (test execution). They operate sequentially — Reci...
- [Help and Support](https://quashbugs.com/docs/reference/help-and-support.md): To get help, reach out to us on Slack, or directly at hamza@quashbugs.com