"Better Bug Reports"

on YouTube ↗08m

" summary

Writes concrete rules: keep titles short and front-load what happened then what caused it (example: System crashes when sorting lists with over 500 items), include clear recreation steps, mark intermittent bugs, and attach environment details (OS, library versions). Uses the mnemonic PEOPLE WORKing to ensure reports cover Problem, Example, Oracle (consistency heuristic / A FEW HICCUPS), Platform, Literate, Extrapolate and Workaround. Recommend saving polished text with Word or Grammarly and include viable workaround to avoid release delays.

AI-written summary · about

" chapters (10)

1. 0:00Good Bug Reports
2. 1:10Bug Report Titles
3. 2:45Problem
4. 3:28Example
5. 4:33Oracle
6. 5:48A FEW HICCUPPS
7. 6:23Platform
8. 6:41Literate
9. 7:18Extrapolate
10. 7:51WORKaround

" related talks

• 30mReporting Bugs: Errors Made and Lessons LearnedPeter Sabev · TestCon Europe 2019
• 46mBugsSam Kalman · Unite 2008
• 16mBug Report — A Developer Task or a Serious Document?Artem Bykovets · QA Fest 2016
• 38mLearning from your bugsHenrik Warne · Jfokus 2019
• 36mFixing Flaky Tests Like a DetectiveSonja Peterson · RailsConf 2019
• 01h 05mBack To Basics: Debugging TechniquesBob Steagall · CppCon 2021
• 04mWhat Bug Hunting Taught Me About Hunting BugsAdi Shacham Shavit · CppCon 2018
• 23mTroubleshooting the fudge out of itCorina Adina Pip · HUSTEF 2019