Troubleshooting the fudge out of it
summary
Testers take on root‑cause troubleshooting, not just test case writing: reproduce the bug three times, compare builds, flags, dependency versions and hardware, and read timestamps in logs — the log is the team’s best friend. Use browser dev tools for client errors. A bug labelled “random” sat for two years until differing input data proved it deterministic; a fix required a 20 minute fix plus code review and five minutes of testing and it resolved the issue.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:40What is the fudge
- 1:41Reproduce the issue
- 4:46Use the same steps
- 5:05Use special characters
- 7:35Track the issue
- 8:21Leads
- 8:35Environments
- 13:40Logs
- 15:18Browser
- 15:36Dev Tools
- 16:11Talking out loud
- 17:55Trying different paths
- 18:52Questions
related talks
24mHow to solve intermittent issues, aka Random Failures
36mFixing Flaky Tests Like a Detective
35mEffective Debugging of Non-Reproducible Bugs
38mLearning from your bugs
36mHow to defuse a bomb Wait, I mean a bug
01h 19mYou Can't Test This? Hammertime!
01h 05mBack To Basics: Debugging Techniques
43mAutomated Tests Are Not Enough