BugBrainDocs
bugbrain.techOpen app

Mobile testing

How to run AI mobile testing in BugBrain — upload an Android build (APK/AAB), optionally add in-app login, and let the AI explore your app on a real device on a cloud device farm, finding and validating crashes, ANRs, and other issues with zero test scripts. A metered add-on.

Mobile testing uploads your Android build to a real device on a cloud device farm and lets the AI explore it like a real user — finding and validating crashes, ANRs, and other issues without you writing a single test script. This guide covers launching a mobile run and reading the results. It is a metered add-on, so it must be enabled for your workspace first.

What it is#

You upload an Android build — an APK or AAB — and BugBrain installs it on a real device hosted by a cloud device farm provider (AWS Device Farm). The AI drives that device remotely, navigating the app like a person would, and watches for problems as it goes. There are no scripts to write and no device lab to maintain.

Along the way it detects and validates issues — crashes, ANRs (App Not Responding, where the UI thread is blocked too long), and other functional or visual problems — and recommends test cases based on what it explored.

A few terms:

  • Cloud device farm — real devices hosted by a provider that the AI drives remotely.
  • ANR — App Not Responding; the UI thread blocked too long. Reported as a high-severity finding.

Why use it#

  • Real device, real behavior — your build runs on real hardware, so you catch problems that only show up off the emulator.
  • Zero test scripts — the AI explores the app on its own; you don't author or maintain mobile test code.
  • Validated findings — issues are confirmed rather than just flagged, and the run recommends test cases you can keep.

Before you start#

Mobile testing is a metered, feature-flag-gated add-on. Before the page works for your workspace:

  • A super-admin must turn on the mobile-testing feature flag and grant a monthly mobile-test quota above zero. If the flag is off or the quota is 0, the page shows a "not enabled" notice with an upgrade or contact path.
  • You need an Android build — an APK or AAB file — to upload.
  • You need permissions: mobile-testing:view to see mobile testing and the execute permission to launch a run.

Only test apps you're allowed to

A mobile run installs and drives your build on a real device and exercises whatever backend it talks to. The launch step requires you to acknowledge a right-to-test attestation. Only run builds you own or have explicit permission to test.

Launch a mobile test#

  1. Open Mobile testing

    Go to Projects → Mobile for your project.

  2. Upload your Android build

    Upload the APK or AAB you want to test.

  3. Add login (optional)

    If the app has a sign-in screen, add in-app login credentials so the AI can get past it. They're encrypted at rest.

  4. Acknowledge and launch

    Acknowledge the right-to-test attestation, then start the run. One run is metered against your monthly quota.

Read the results#

When a run finishes, BugBrain reports what the AI did and what it found.

  • Validated findings — confirmed crashes, ANRs, and other issues, with severity and evidence.
  • Recommended test cases — test cases the AI suggests based on the flows it explored.
  • Trajectory — the steps the AI took on the device, so you can see how it reached each finding.

Add login to go deeper

Without credentials the AI can only explore what's reachable before sign-in. Adding in-app login lets it reach the authenticated parts of your app, where most real bugs live.

Test runsSee how runs are organized and reviewed.Issues & bug triageAct on the crashes and ANRs a run surfaces.Test casesKeep the test cases a run recommends.

Frequently asked questions

What do I upload to run a mobile test?

An Android build — an APK or AAB file. BugBrain installs it on a real device on a cloud device farm and drives it like a real user. You can optionally add in-app login credentials so the AI can get past a sign-in screen; they're encrypted at rest.

What kind of device does my app run on?

A real, physical device hosted by a cloud device farm provider (AWS Device Farm). The AI drives the device remotely — taps, swipes, and types — so you test on real hardware without maintaining a device lab.

What is an ANR?

ANR stands for App Not Responding — it happens when the app's UI thread is blocked too long and the system would show a "close app?" dialog. BugBrain detects ANRs and reports them as high-severity findings alongside crashes.

Why do I have to acknowledge a right-to-test attestation?

Mobile testing drives a real device against your build and any backend it talks to. Before launching, you confirm you're authorized to test the app — only run builds you own or have explicit permission to test.

Why do I see a "not enabled" notice?

Mobile testing is a metered add-on. It needs the mobile-testing feature flag on and a monthly mobile-test quota above zero. If either is missing, the page shows a "not enabled" notice with an upgrade or contact path.