FlyTrap Explorative testing

Nobody wrote
these tests.

FlyTrap opens your build, taps through it like a curious user, and turns what it finds into a suite. You get a map of the app, not a blank page and a tired login script.

The method

Not random tapping. A loop with a reason.

Every step is a decision you can read. The crawler scores what to try next, acts on a real device, and keeps the paths worth running again.

  1. 01

    Read the screen

    Every frame becomes a fingerprint from the view tree, text, and layout. The crawler knows if it has been here before.

  2. 02

    Pick the next move

    Auth, money, and data entry outrank settings toggles. Dead ends lose priority so time goes where bugs live.

  3. 03

    Act like a person

    Tap, type, scroll, rotate, grant permissions, follow deep links. On real hardware, not a cartoon of a phone.

  4. 04

    Keep what matters

    Paths get a risk score from crashes, network errors, and how close they sit to revenue. High scores become tests.

What it produces

A map of your app, redrawn every build

Ten screens, nine transitions, one dead end at payment. Nobody described any of this beforehand.

Into the suite

The paths worth keeping

Exploring only matters if something runnable comes out. High-risk flows get promoted and run again on the next build.

Guest checkout with coupon functional 0.91 Promoted

Valid coupon rejected at the last step

Sign in with Google functional 0.84 Promoted

Consent screen returns to a blank view

Deep link to a removed product deeplink 0.78 Promoted

No empty state, spinner never stops

Reorder from order history regression 0.62 Promoted

Reached at depth 3, nothing broke

Change notification prefs regression 0.19 Queued

Small blast radius, kept for later

Point it at a build and watch the map fill in

No scripts, no selectors, no test plan first. Drop an APK or connect TestFlight.