Use cases

The scenarios teams automate with Drizz — onboarding, authentication, search, checkout, navigation and full regression suites.

Platforms	Android · iOS · Mobile web
Best for	End-to-end functional flows,
Also handles	Cross-app flows, location-dependent flows, API-seeded data
Watch out	Secure screens — payment PIN entry renders black to any capture tool, Drizz included

Prerequisites

• Drizz desktop app installed and signed in

• The app under test registered

• A login_module module, for the checkout example below — see Modules

Scenarios

Scenario	Covers
User onboarding	First launch, permission prompts, profile setup, tutorial skips
Authentication	Login, OTP, social sign-in, logout, session expiry
Search & filter	Query entry, result lists, sort and filter combinations, empty states
Product & catalog	Category browsing, product detail, variants, wishlists
Checkout & payment	Cart, address, coupons, order summary, confirmation
App navigation	Tab switching, deep links, back behavior, state after backgrounding
Regression suites	All of the above, across devices, on every release

Each is an ordinary Drizz test. None requires a different tool or a special mode.

Copy this

A checkout flow against ShopEase, the demo app used throughout these docs.

# ShopEase — add to cart and reach checkout

CALL login_module

Tap on the search icon
Type running shoes in the search field
Tap on the first search result
Wait Until 3 Seconds

Store the price as listed_price
Tap on Add to Cart
Wait Until 2 Seconds

Validate that Item added to cart is visible

Tap on the cart icon
Wait Until 2 Seconds

Validate that the total matches {{listed_price}}
Tap on Proceed to Checkout
Wait Until 3 Seconds

Validate that the checkout page is visible

CLEAR_APP com.shopease.android

Beyond a single app

Flows	Action items
Flows that leave your app	An OTP arriving in the SMS app, a payment handoff, an OAuth screen in a browser
Location-dependent flows	Set a location with SET_GPS(latitude=, longitude=) before the app reads it
Data-seeded flows	Call your own API mid-test to create the state a scenario needs, then assert the UI matches — see API steps
Many accounts or environments	One script, one dataset per environment

Worked examples of each are in Recipes.

Common mistakes

What you do	What happens
Put a 60-step journey in one test	A failure mid-flow is hard to isolate and stabilize. One scenario per test is the pattern these docs assume
Assert on a payment PIN screen	The screen renders black to any capture tool, Drizz included
Automate a device matrix before one device is stable	Every device repeats the same failure

Next

• Quickstart: your first test

• Recipes

• Known limitations

---

Last updated: 6 August 2026