Modern QA2026Isolation: Narrowing Down the Bug — tiles
Log inJoin
40 / 71 · 11 Manual Testing Fundamentals · Effective Bug Reports← prev⊞ allnext →☰ Read as one page

5.6Isolation: Narrowing Down the Bug

Before filing, try to narrow the scope. The narrower your report, the faster the fix.

Questions to Ask Yourself

  1. Browser-specific? Try in Chrome, Firefox, Safari. If it only happens in one, note that.
  2. Environment-specific? Does it happen in staging and production, or just staging?
  3. Data-specific? Does it happen with any email, or only emails with special characters?
  4. Timing-specific? Does it happen every time, or intermittently?
  5. Permission-specific? Does it happen for all users, or only certain roles?

Intermittent Bugs

These are the hardest to report. For intermittent bugs:

  • State the reproduction rate: "Reproduces approximately 3 out of 10 attempts"
  • Describe what you tried that did NOT trigger the bug
  • Note any patterns: "Seems to happen more often right after deployment"
  • Include timestamps of occurrences so the team can check logs