Completion, inline errors and snippets for the whole YAML command set. No driver boilerplate, no page objects.
The inspector mirrors the live device. Click an element and drop a working step into your flow.
Every failed step comes with the screenshot, the network calls around it and the device log.
The in-app interceptor streams your app’s traffic into Dev Scenario. Each run keeps the calls it made, so a failed step shows the request behind it.
Return any status code for any call and see how the app copes. Testing a 500, a 401 or a timeout becomes a two-click job.
One call, a different answer each time. Test an OTP screen that lets the user request a code three times, then blocks them — fully automated.
Run a scenario against the real backend and every request and response is captured. Save them as a mock group, and from then on the app is tested against that exact contract — a staging outage or a half-deployed API no longer turns your suite red.
Run “Checkout” on a device against the live backend. Every call lands in the run.
Save the run’s traffic as a mock group. Requests match on method, path and body — not on tokens or timestamps.
Turn the group on for the scenario. Same requests, same responses — on every run, locally and in CI.
Browse your App Distribution releases inside Dev Scenario. Choose a build and a device — the APK is downloaded, installed and put through your regression suite, with results per scenario. Then watch Crashlytics in the same place: top issues, trends and stack traces, one click from a bug report.
Keep text and test data out of your flows. The same unit runs in every language your app ships, for every kind of user, with big fonts or no network — without a single copied test.
Reference a key instead of the text. Dev Scenario detects the language the app is showing and checks the right string.
Logins, cards and test data live in profiles. Pin a profile to a scenario or chain and run the same flow as anyone.
Put the phone in the state your users are in, right from the flow, and check the app still holds up.
Biometric logins, selfie capture, payments behind test switches — if your app has a test-only path, a flow can turn it on.
Simulate a fingerprint on the device and check what your app does with it — no real finger, no manual step.
Send any custom value from the flow straight into the running app. Your code reads it like any system property and takes its test path — mock the selfie camera, skip a captcha, switch a feature on.
Flows you write in the app run unchanged in any pipeline. Each run writes JSON events and run artifacts your tooling can read.
CI setup guide →Banks, fintechs and regulated apps run Dev Scenario on their own machines and build agents.
Talk to sales