# Quash Documentation ## Docs - [Adding an App](https://quashbugs.com/docs/apps/adding-an-app.md): Apps is where you register and configure the applications you want to test in Quash. It is a top-level section in the left navigation panel — the same level as Test Studio, Suites, and Tasks. - [Builds](https://quashbugs.com/docs/apps/apps-manager/builds.md): The Builds tab is where you upload the application binaries that Quash installs and runs tests against. - [Apps Manager](https://quashbugs.com/docs/apps/apps-manager/index.md): The Apps Manager - [Knowledge](https://quashbugs.com/docs/apps/apps-manager/knowledge.md): The Knowledge tab is where you connect your app's codebase and where the agent's Guidance profile lives. Together these two things give Recipe the deepest possible understanding of how your app act... - [Overview](https://quashbugs.com/docs/apps/apps-manager/overview.md): Overview Tab - [Credentials](https://quashbugs.com/docs/apps/credentials.md): The Credentials tab is where you store the login details and authentication tokens the agent uses to access your app during testing. Instead of hardcoding credentials into test prompts or task inst... - [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 ... - [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... - [iOS Simulators (Mac only)](https://quashbugs.com/docs/devices/ios-simulators-mac-only.md): To run tests on an iOS simulator through Quash: - [Local Emulators](https://quashbugs.com/docs/devices/local-emulators.md): To run tests on an emulator through Quash: - [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): To connect your real devices locally to Quash: - [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: - [Report Dashboard](https://quashbugs.com/docs/execution-reports/report-dashboard.md): Every task and suite you run on Quash generates an execution report automatically. As soon as a run finishes, the report is ready — no setup required. The Reports section is where all of these live... - [Sharing and Downloading Reports](https://quashbugs.com/docs/execution-reports/sharing-and-downloading-reports.md) - [Guidance](https://quashbugs.com/docs/getting-started/core-concepts/guidance.md): Guidance is the knowledge the Abgumi agent builds for itself as it tests your app. You do not write it. You do not configure it. It accumulates automatically — session by session — as Mahoraga inte... - [Core Concepts](https://quashbugs.com/docs/getting-started/core-concepts/index.md): Quash works differently from traditional test automation tools. There are no scripts to write, no selectors to define, no frameworks to configure. Instead, you describe what you want to test in pla... - [Megumi & Mahoraga](https://quashbugs.com/docs/getting-started/core-concepts/megumi-and-mahoraga.md): Quash is powered by two AI agents. They have distinct roles — one thinks, one acts. Understanding what each one does, and where the boundary between them is, is the foundation for using Quash effec... - [Memory](https://quashbugs.com/docs/getting-started/core-concepts/memory.md): Memory is how Quash builds and maintains context. It determines how well the Abgumi agent understands your app, your requirements, and your intent before generating a single test case — and how tha... - [Tokens & /compact](https://quashbugs.com/docs/getting-started/core-concepts/tokens-and-compact.md): Every recipe session in Test Studio has a context window — a limit on how much the Recipe agent can hold in active memory at once. Understanding why this limit exists and how Quash handles it will ... - [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 ... - [Platform Overview](https://quashbugs.com/docs/getting-started/platform-overview.md): Quash is a desktop application with a left navigation panel, a central workspace, and context panels that slide in from the right. This page maps every section of the interface so you know where ev... - [Quickstart Guide](https://quashbugs.com/docs/getting-started/quickstart-guide.md): Get from zero to your first test result in 5 minutes. This guide uses a local Android emulator — the fastest path to a working test with no hardware required. - [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. - [Jira](https://quashbugs.com/docs/integrations/jira.md): The Jira integration does two distinct things: it automatically creates issues when tests fail, and it lets you attach Jira tickets as context when generating tests in Test Studio. Both require Jir... - [Notion](https://quashbugs.com/docs/integrations/notion.md): Connecting Notion links your Quash workspace to your Notion account for documentation and reporting workflows. - [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. - [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 - [Organization & Members](https://quashbugs.com/docs/reference/organization-and-members.md): The Organization & Members section is where you manage everything related to your workspace in Quash. From here, you can view and update your personal profile, check organization details, configure... - [Troubleshooting](https://quashbugs.com/docs/reference/troubleshooting/index.md): This section covers the most common issues you may encounter with Quash and Mahoraga. Use the descriptions below to find the right page for your problem. - [Test Studio Issues](https://quashbugs.com/docs/reference/troubleshooting/test-studio-issues.md): This page covers issues with the Megumi agent, recipe sessions, generated test quality, and memory behaviour. - [Connections](https://quashbugs.com/docs/running-tests/backend-validations/connections.md): A connection is the configuration Quash uses to reach your backend. It defines where your API lives, how to authenticate with it, and any headers required to make a valid request. Every validation ... - [Creating a Validation](https://quashbugs.com/docs/running-tests/backend-validations/creating-a-validation.md): A validation is a specific backend check — one API call, with defined expected responses and assertions. You build it on top of a Connection, which handles authentication. The validation itself def... - [Backend Validations](https://quashbugs.com/docs/running-tests/backend-validations/index.md): Backend Validations let you verify what happens in your backend while Mahoraga interacts with the UI. When a user action triggers an API call, changes data in a database, or updates server state, y... - [Using @slug in Prompts](https://quashbugs.com/docs/running-tests/backend-validations/using-slug-in-prompts.md): Once a validation has a prompt action enabled, you can call it inline inside any task prompt by typing `@`. The validation runs at exactly the point in the sequence where you place it — not before,... - [Creating a Suite](https://quashbugs.com/docs/running-tests/suites-overview/creating-a-suite.md): This page walks through creating a suite from scratch, adding test cases, configuring execution mode, and running it for the first time. - [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... - [Sequential vs. Isolated](https://quashbugs.com/docs/running-tests/suites-overview/sequential-vs.-isolated.md): Every suite runs in one of two execution modes. Choosing the right one is the most important configuration decision you make when building a suite — it determines whether tests share state, run in ... - [Creating and Running a Task](https://quashbugs.com/docs/running-tests/task-overview/creating-and-running-a-task.md): A task is a single plain English instruction you give to Mahoraga. It is the most direct way to test something in Quash — no suite setup, no library, no configuration required. Describe what you wa... - [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... - [Prompting guide (task execution)](https://quashbugs.com/docs/running-tests/task-overview/prompting-guide-task-execution.md): A task prompt is a plain English instruction given directly to Mahoraga — the execution agent. Unlike Test Studio prompts that ask Recipe to _generate_ test cases, task prompts are _executed immedi... - [Rerun](https://quashbugs.com/docs/running-tests/task-overview/rerun.md): When you run a task for the first time, Mahoraga operates in full reasoning mode - reading each screen, identifying elements, handling interruptions, and making decisions at every step. When the ru... - [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... - [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 ... - [Creating a Test Case](https://quashbugs.com/docs/test-management/test-case/creating-a-test-case.md): There are two ways to create test cases in Quash: manually using the + New Test Case panel, or by generating them in Test Studio and saving them to the library. Manual creation gives you full contr... - [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... - [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. - [Creating Datasets](https://quashbugs.com/docs/test-management/test-data-overview/creating-datasets.md): A dataset is a named table of input values. Each column is a type of input. Each row is one complete set of inputs for a single test run. You can create datasets manually by building the table dire... - [Importing from File](https://quashbugs.com/docs/test-management/test-data-overview/importing-from-file.md): If your test data already exists in a spreadsheet, a CSV export, or a JSON file, you can import it directly into Quash instead of entering values by hand. - [Test Data Overview](https://quashbugs.com/docs/test-management/test-data-overview/index.md): Test Data is where you store the structured inputs your tests depend on — login credentials, form values, search terms, product details, user profiles, or any other data your app needs during a tes... - [Using /slug in Prompts](https://quashbugs.com/docs/test-management/test-data-overview/using-slug-in-prompts.md): Once a dataset exists, you reference it in any task or recipe prompt using its slug. The slug is the short identifier you set when creating the dataset — always prefixed with `/`. - [Collaboration as a team](https://quashbugs.com/docs/test-studio/collaboration-as-a-team.md): Test Studio is built for teams, not individuals. A recipe can bring together inputs from across your team — product, design, engineering, and QA — in a single session. Megumi reads all of it simult... - [Configuration in Test Studio](https://quashbugs.com/docs/test-studio/configuration-in-test-studio.md): The CONFIG panel controls how Megumi generates tests — how thorough, what type, which platform, and what kinds of validations to include. Set it before your first prompt to shape everything Megumi ... - [Overview](https://quashbugs.com/docs/test-studio/overview.md): Test Studio is where you generate test cases from plain English. No scripting. No selectors. No test frameworks to configure. Describe a feature or a flow, and Quash builds a ready-to-run set of te... - [Common mistakes](https://quashbugs.com/docs/test-studio/prompting-guide-test-generation/common-mistakes.md): These are the prompting errors that most frequently lead to generic, incomplete, or unusable test output from Megumi. Each one has a specific fix. - [Prompting guide (test generation)](https://quashbugs.com/docs/test-studio/prompting-guide-test-generation/index.md): The quality of your prompts directly determines the quality of the tests Megumi generates. A vague prompt produces generic tests. A specific, well-structured prompt produces tests you can run immed... - [Prompt patterns & examples](https://quashbugs.com/docs/test-studio/prompting-guide-test-generation/prompt-patterns-and-examples.md): These are five proven prompt patterns that produce consistently good output from Megumi. Each one works best for a specific type of testing need. Use them as starting templates and adapt to your fe... - [Writing effective prompts](https://quashbugs.com/docs/test-studio/prompting-guide-test-generation/writing-effective-prompts.md): This page covers how to get the most out of every prompt you send to Megumi — how expected outcomes turn into assertions, how to leverage multiple context sources, how to ask Megumi questions beyon... - [Attaching Context](https://quashbugs.com/docs/test-studio/recipe/attaching-context.md): The quality of the tests Recipe generates is directly proportional to the context it has before it starts. A prompt with no context produces generic steps that could describe any app. The same prom... - [Recipe](https://quashbugs.com/docs/test-studio/recipe/index.md): A recipe is a Test Studio session. Each recipe holds a complete conversation with the Megumi agent — your prompts, the agent's responses, and every test case generated in that session. It is a pers... - [Saving Generated Tests](https://quashbugs.com/docs/test-studio/saving-generated-tests.md): When Megumi generates test cases in a session, they live in the Tests panel until you decide what to do with them. You have two options: save them to your Test Cases library, or add them directly t... - [Token Management](https://quashbugs.com/docs/test-studio/token-management.md): Every Test Studio session operates within a token budget. Tokens are a measure of how much context the Megumi agent is actively processing — your prompts, the agent's responses, attached documents,... ## OpenAPI Specs - [openapi](https://quashbugs.com/docs/api-reference/openapi.json)