Plain-English test authoring
Describe app interactions to generate executable tests. Test generation, editing, and change intelligence are unlimited on all plans; execution uses tokens.
Write mobile tests in plain English, run them on real devices, and inspect failures.
Drizz is a Vision AI mobile testing platform for QA and engineering teams working on iOS and Android apps. Connect an app build, describe a user flow in plain English, and run the generated test on real devices. Visual execution resolves steps against the rendered interface rather than relying only on stored selectors. Teams can inspect steps and approve changes, manage suites and builds, and review failure evidence. Automated checks support release decisions; they do not guarantee that an app is bug-free.
Describe app interactions to generate executable tests. Test generation, editing, and change intelligence are unlimited on all plans; execution uses tokens.
Use screen understanding to resolve test steps and adapt to UI changes, with steps and proposed changes available for review.
Execute mobile tests on real iOS and Android devices and include runs in CI pipelines.
Organize apps, builds, plans, devices, and environments, and inspect run history for recurring release checks.
Inspect root-cause reports with executed steps, screenshots, application state, and logs to distinguish app failures from UI or environment changes.
Combine API and backend validation with UI flows. The platform also provides accessibility testing for mobile journeys.
Check login, onboarding, checkout, and other recurring user journeys after a build changes.
Use screenshots, logs, and recorded steps to reproduce failures and decide whether the app or the test needs correction.
Compare critical flows across iOS and Android hardware, with engineers reviewing results before shipping.
Trial is free with 300 tokens, one app, and one seat. Solo is $49 per month with 5,000 tokens, two apps, one seat, and one parallel execution. Team has custom token volume, parallel execution, apps, and seats.
One token covers one executed test step, including steps in failed runs. A ten-step test uses ten tokens each time it runs. Writing and editing tests, change intelligence, RCA reports, and MCP access are not metered.
Execution is blocked until tokens are topped up. Writing and editing tests remain available without consuming tokens.
Solo and Team include a Drizz engineer for setup, initial suites, and issues involving your app. This support and parallel execution are not included in Trial.
The terms require an authorized corporate customer. Teams need an app build and the rights to upload and process its data; account access is required for relevant features.
트래픽 데이터는 참고용으로만 확인하세요.