For testers

Takes about 2 minutes

You test the app's QA build on your own phone. Report what looks wrong with a long press; the fix comes back to the same phone for you to check.

Install the QA build

  1. Open the install page your team shares, or the View app button on a merge request.

  2. Tap Install build #N. Android may ask you to allow installs from your browser. The QA build installs next to the store app.

Pair your phone

  1. On a computer, open https://<hub-host>/sign_in and sign in with GitLab.

  2. The Hub shows a QR code. Scan it with your phone's camera and open the link in the QA build.

  3. The app says Paired as @you. The code works once and expires after 10 minutes; reload the page for a new one.

Your reports are filed in GitLab as you, so a Duo flow can pick them up.

Report a bug

  1. Tap the Bugoro button on the screen.

  2. Long press what looks wrong. Bugoro boxes it on a screenshot.

  3. Add a note, pick the type and the severity, and send.

Track it under My reports. If the agent has a question, the report says Question for you: answer it there.

Fix ready, install, Verify

  1. When the report says Fix ready, tap Install build #N. The fix may come from the Duo agent or from a developer: both come back to you the same way.

  2. Open the app on the new build and go through What to retest.

  3. Tap Verify if it's fixed, or Still broken if not, and say what you see.

The fixVerifyStill broken
The Duo agent's merge requestApproves it if you may, and turns on auto merge, pinned to the build you tested: it merges once its pipeline passes. If a safety check stops that, a developer reviews it instead.The agent tries again. After its 2 attempts, a developer takes over.
A developer's merge requestApproves it if you may, pinned to the build you tested, and comments for its author and reviewers. They merge it.Comments on the merge request with your note, mentioning its author. Its next build comes back to you.

Verify and Still broken appear only on the fix build itself. On any other build, older or newer, the app asks you to install the fix build first, so you always vouch for the build you ran.

Before and After

The merge request has a note with emulator screenshots of the reported screen: the default branch's build (Before) and the fix (After). No visible difference means the two shots match. That is expected when a fix isn't visual, or shows only after you tap through the screen: Bugoro doesn't replay your steps. Check it on your phone either way.

When it isn't a UI bug

The flow fixes only the reported screen's UI. For anything else it hands the issue to a developer with a note they can act on, and your report says With a developer. When the developer's merge request closes your report, its build comes back to you for Verify.