TFW you spend a couple hours trying to track down a horribly obscure bug, you're looking at the code blankly and are getting seriously irritated and then it was a typo in your unit-test code.
Replies:
3
@timbray When mentoring junior programmers, I regularly point out if your test fails, that means there is a bug in your code, your test, or both. When they get more experience, I'll add "your understanding" to that list.
@timbray Heh… I remember early on in my career I wrote a program called `test.c` to test the thing… and I was sure it was broken. But, dang, I ran `test` on the Unix prompt and it succeeded.. never output anything either. Two things: 1. I never name things just “test” anymore, and 2. I run all programs in the current working directory always forever as “./<program name>”
@timbray my all-time fav is when I've corrected the bug and I'm not seeing a change happen, like no change in the run at all... bc I forgot to save the file. Still do it from time to time but I've finally le-rned to supect that's what's happened. 😹
