Hacker News Reader

In my world, the test suite is a better “why” than code comments.

What was hard to write should be also hard to read! /s

Why read the code when you can read the out of date comments! /s

If comments are out of date you're not doing code reviews.

How do you tie the test suite to the specification? A test for a certain behavior alone doesn't document why it's testing that.

I have a property on my specification tests called "about" that explains why the feature exists along with other contextual information.

It makes much more sense to centralize the "why does this behaviour exist" there where the specific behaviour is being tested rather than in the code.

Reply on news.ycombinator.com