Modern QA2026Bug Report Workflow — tiles
Log inJoin
41 / 71 · 11 Manual Testing Fundamentals · Effective Bug Reports← prev⊞ allnext →☰ Read as one page

5.7Bug Report Workflow

Filing

  1. Search for duplicates first. Duplicate reports waste everyone's time.
  2. File one bug per report. Do not combine "login fails AND the forgot password link is broken."
  3. Assign to the correct team or component. If unsure, assign to the triage queue.

After Filing

  • Watch for developer questions. Respond within hours, not days.
  • If asked to provide more information, update the bug report itself (not just the comment thread).
  • If you discover additional reproduction steps or a simpler reproduction path, update the report.

Verification

When the fix is deployed:

  1. Reproduce using the original steps — the bug should be gone.
  2. Test related scenarios — did the fix introduce a regression?
  3. Close the bug report with a comment: "Verified fixed in build #4530."