Skip to main content

Common Mistakes in Bug Reports / Bug 报告常见错误

Learn from the most frequent mistakes testers make when writing bug reports.

从测试人员编写 Bug 报告最常见的错误中学习。

Top 10 Mistakes / 十大常见错误​

1. Vague Title / 标题模糊​

  • Bad / 错误: "Login not working" / "登录不工作"
  • Good / 正确: "[Login] Facebook OAuth login returns 500 error on iOS" / "[登录] iOS 上 Facebook OAuth 登录返回 500 错误"

2. Missing Environment Details / 缺少环境信息​

  • Always include: device, OS, browser, app version / 始终包含：设备、操作系统、浏览器、应用版本

3. Incomplete Reproduction Steps / 复现步骤不完整​

  • Start from a known state / 从已知状态开始
  • Don't assume developers know the flow / 不要假设开发人员了解流程

4. No Attachments / 缺少附件​

  • Screenshots are not optional / 截图不是可选项
  • A picture is worth a thousand words / 一图胜千言

5. Combining Multiple Bugs / 混合多个 Bug​

  • One bug per report / 一个报告一个 Bug
  • Different issues need different fixes / 不同问题需要不同修复

6. Wrong Severity / 严重等级错误​

  • Every visual bug is not "Critical" / 不是每个视觉 Bug 都是"致命"
  • Payment bug is not "Minor" / 支付 Bug 不会是"轻微"

7. Using Subjective Language / 使用主观语言​

  • Avoid / 避免: "This is annoying", "Bad design" / "这很烦人", "糟糕的设计"
  • Use / 使用: "Button is misaligned by 10px to the left" / "按钮向左偏移了 10px"

8. Not Checking Prerequisites / 未检查前置条件​

  • Is the user logged in? / 用户是否已登录？
  • Is payment method configured? / 是否配置了支付方式？

9. Missing Expected Behavior / 缺少预期行为​

  • What should happen? / 应该发生什么？
  • Reference the requirement if possible / 如有可能，引用需求

10. Poor Formatting / 格式混乱​

  • Walls of text are hard to read / 大段文字难以阅读
  • Use structured format with clear sections / 使用清晰的结构化格式