Lesson 82 · Build with customers
How do I have BuildBetter test my app before each release?
AI testers, test flows and reproduced bugs.
You’ll be able to
- Choose the journeys your app should pass
- Review reproduced bugs and replays
- Route findings into your team's work
Read the docs
Synced from docs.buildbetter.aiThe help pages for this lesson, kept up to date. Read them here without leaving the lesson.
Transcript
You can now have BuildBetter test your app before each release, then turn reproduced bugs into work for your team.
In Build, open QA Agent. Your QA team explores test flows, checks layout, and retries suspected bugs from a clean start.
Under Test flows, review each start page and what it tests. Edit test flows controls which journeys are included.
Open QA Agent settings. Next to Automatic runs, choose Edit. Under When, choose a nightly schedule or a GitHub release trigger.
Run now opens an on-demand check. Review the selected test flows and credit limits before starting. Each run uses credits.
Open a completed run under Recent runs. Review the test flows, verified bugs, and anything that needs another look.
Open a finding for its steps, expected result, and actual result. Reproduced tells you how often it happened from a clean start.
Watch the Replay alongside the recorded agent actions. Check the evidence before deciding what to fix.
File to Inbox adds a bug to your team's work. Send to hands the same brief to a coding agent. We'll cover that handoff at the end.
Next up, run an AI interview study and recruit people.
