2 ms·
The thing I tell people when I’m critiquing their tests is that nobody gives a shit about your tests until they break, at which point they’re interacting with y
by hinkley 5y ago
The thing I tell people when I’m critiquing their tests is that nobody gives a shit about your tests until they break, at which point they’re interacting with your code when they’re already in a bad mood.
They will associate that feeling with you. So do you want to make their bad day worse by writing abstruse code? Or should they be simple?
I know I’m “done” with a test when I know why it’s red from what’s in the console. I shouldn’t even have to look in the source code. Until then, my tests are a work in progress.
We could apply this philosophy a lot more widely.
- akkartik 5y agoTotally agreed! Here's a prototype from a few years ago where I tried to make this easier: https://github.com/akkartik/mu1#readme https://github.com/akkartik/mu1#readme (read just the first few paragraphs) I still think the full answer lies in this direction.