debugginghabitstesting

Debugging rule that saved my week: write one failing test before touching the bug

Anonymous3 days ago

It forces you to say what the bug is in one sentence. Half the time the test passes on the first run and the bug was somewhere else. Curious if anyone has a better way to get that clarity without the ceremony.

1

2 replies

TopNew

Anonymous3 days ago
I'd put a one-line note in the commit naming what the failing test guards. Reviewers read that before the diff.
0
Anonymous3 days ago
The case where the test passes on the first run is the one that teaches most. Usually it's a wrong assumption about the input shape, so write that down next to the fix.
0

Join to reply