Reporting Bugs: Errors Made and Lessons Learned
summary
Covers 15 common problems with concrete fixes: require steps to reproduce, attach screenshots or video using Greenshot and TinyTake, add expected vs actual, and set non‑default priority/severity with a simple mapping script. Recommends automated sanity tests under five minutes, semantic versioning, recovery curl snippets, VM/snapshot rollback, and crowdtesting. Gives quantifiable anecdotes (over 2500 "it doesn't work" reports) and shows formatted examples that cut triage time and make failures reproducible.
AI-written summary · about
chapters (29)
- 0:00Bug reporting intro
- 1:49Why accurate reports matter
- 4:01Fifteen bug-reporting mistakes
- 5:24Avoid duplicate reports
- 6:06Reproducibility in reports
- 7:50Describing symptoms precisely
- 9:17Steps to reproduce essential
- 10:24Expected vs actual results
- 10:47Priority and severity setting
- 12:54Testing correct environment
- 13:37Attach screenshots and videos
- 14:21Why incomplete reports fail
- 15:05Avoid multiple issues in one
- 16:31Investigate beyond obvious
- 17:40Include relevant code snippets
- 18:02Avoid overly technical reports
- 18:46When to stop investigating
- 19:08Backup and restore importance
- 20:14Facts vs observations
- 20:36Formatting reports clearly
- 23:55Color coding effectively
- 24:40Automate report generation
- 25:22Choosing the right words
- 26:06Consistency in reports
- 27:13Structuring long descriptions
- 27:56Avoid redundancies
- 28:40Peer review and practice
- 29:23Crowd testing for improvement
- 30:04Final thoughts and Q&A
