Platform Overview

The Interface

When you open Quash, you see three areas: Left navigation panel — the vertical sidebar on the left. This is how you move between every major section of Quash. It stays visible at all times. Central workspace — the main area where you do your work. What appears here changes depending on which section you have open — a recipe conversation in Test Studio, a list of test cases in Test Cases, a report detail view in Reports. Right-side panels — slide-in panels that appear when you click controls on the right edge of the screen. In Test Studio, these include the TESTS panel (showing generated test cases) and the CONFIG panel (controlling how Recipe generates tests). In Reports, the Device View panel shows the screen recording. The profile button in the top-right corner opens your account settings, organisation details, device management, and integrations.

What Each Section Does

The left navigation panel contains every top-level section in Quash.

Section	Purpose
Test Studio	Where you generate test cases using the Recipe agent. Open a recipe, attach context (your app, GitHub branch, Figma designs, Jira tickets, PRDs), write a prompt, and Recipe produces structured, executable test cases. This is where most test creation happens.
Test Cases	The central library of all your saved test cases — whether generated by Recipe or written manually. Search, filter, edit, tag, and add them to suites from here.
Tasks	Ad-hoc test execution. Write a single plain English instruction, pick a device, and run it immediately. No suite setup required. Best for quick checks and one-off exploration.
Suites	Collections of test cases grouped to run as a unit. Create suites, add test cases from your library, choose sequential or isolated execution mode, and trigger runs across one or more devices.
Apps	Where you configure everything Quash needs to understand your application. Each app has five tabs: Overview, Builds, Knowledge, Credentials, and Test Data. The deeper you configure an app, the more specific and accurate your generated tests become.
Validations	Backend validations — API calls that run during test execution to verify backend state matches what the UI shows. Create connections to your API, define validations with expected responses, and reference them in prompts using @slug.
Test Data	Structured datasets of test inputs — credentials, form values, product details — stored as named tables. Reference a dataset in any prompt using /slug, and Quash runs the test once per row automatically.
Reports	Every task and suite run generates an execution report. The Reports section shows a dashboard of all runs, with filters by type and result. Open any report to see the AI-written executive summary, observations, step-by-step breakdown with screenshots, and the full device screen recording.

The profile menu in the top-right also gives access to:

Devices — connect and manage physical Android devices, local emulators, iOS simulators, and Quash cloud devices.
Integrations — connect Jira, GitHub, Figma, Slack, and other external tools.
Organisation & Members — manage your team, invite members, set roles and permissions.
Settings — organisation-level configuration including maximum concurrent tasks and ADB path.

The Typical Workflow

Most teams follow this path once they are set up:

Open Test Studio and create a recipe for the feature you are testing.
Attach context — your app, a GitHub branch, Figma designs, a PRD, a Jira ticket. The more you attach, the better the output.
Write a prompt describing what you want to test. Recipe generates test cases.
Review and save the generated tests to your Test Cases library.
Add test cases to a suite and run the suite on your connected devices.
Read the execution report — executive summary, observations, step-by-step screenshots, and the device recording.

For quick one-off checks, skip steps 1–4 and go straight to Tasks — write a prompt and run it immediately on any connected device.

Where to Find Things

I want to…	Go to
Generate test cases from a prompt or spec	Test Studio
Write a test case manually	Test Cases → + New Test Case
Run a quick one-off test	Tasks → + New Task
Run multiple tests together	Suites
Upload an APK build	Apps → [your app] → Builds
Connect my GitHub repository	Apps → [your app] → Knowledge
Store login credentials	Apps → [your app] → Credentials
Create a test data dataset	Test Data → + New Dataset
Set up a backend API validation	Validations → Create Connection
Connect a device	Profile → Devices → Scan for devices
See all test results	Reports
Share a report externally	Reports → [report] → Share
Connect Jira	Profile → Integrations → Jira
Manage team members	Profile → Organisation & Members
Review what the agent has learned	Apps → [your app] → Knowledge → Guidance

Next steps

If you are setting up Quash for the first time:

Quickstart — get your first test running in 5 minutes
Devices — connect a physical device, emulator, or cloud device
Apps — configure your app, upload a build, and connect your codebase

Getting started

Devices

Apps

Test Studio

Test Management

Prompting Fundamentals

Running Tests

Execution Reports

Integrations

Quash MCP

Account & Organization

Reference

The Interface

What Each Section Does

The Typical Workflow

Where to Find Things

Next steps

​The Interface

​What Each Section Does

​The Typical Workflow

​Where to Find Things

​Next steps

The Interface

What Each Section Does

The Typical Workflow

Where to Find Things

Next steps