Lesson 111 · Build with customers
What should I do with a QA finding?
Review evidence and intended behavior. Find duplicates or file a bug.
You’ll be able to
- Review evidence and intended behavior
- Find duplicates or file a bug
- Track the fix and its recheck
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 turn the QA review queue into clear decisions and track the fix afterward.
Open Findings and choose Needs review to find decisions that are still waiting.
Filter by reproduction, review state, fix status or category to narrow the queue.
Open a finding and read what happened. Check the reproduction attempts before deciding it is a bug.
If the behavior is intended, describe why and choose whether the note applies to this flow or all flows.
If another bug already covers it, Mark duplicate lets you find that original instead of filing more work.
For a new bug, review File to Inbox. The filed link shows where the work went.
Use Link a fix to connect the pull request, ticket or project that tracks the repair.
A linked fix can ship before it is rechecked. Read the later result before treating the finding as resolved.
Next up, run an AI interview study and recruit people.
