Introducing FlutterProbe: end-to-end tests in plain English

Mobile end-to-end testing has always asked teams to choose between two bad options: slow, flaky integration_test runs, or brittle scripts that break the moment the UI shifts. We built FlutterProbe because our own client work needed something faster and more durable.

Why we built it

On large Flutter apps, a full integration suite can take many minutes per run. That latency kills the feedback loop — developers stop running tests locally, and regressions slip into review. We wanted round-trips fast enough to feel instant.

• Plain-English flows — describe what a user does, not which keys to tap.
• Direct widget-tree access — no screenshot diffing, no fragile coordinates.
• Sub-50ms round-trips — fast enough to run on every save.

How it compares

FlutterProbe is an open-source alternative to integration_test and Patrol. Where those drive the app from the outside, FlutterProbe talks to the widget tree directly — which is what makes it both faster and less brittle when layouts change.

The goal is simple: make the fast path the default path. If tests are instant, people actually run them.

Learn more at flutterprobe.dev, and the source is public on GitHub. Issues and contributions are welcome.