Hacker News new | ask | show | jobs
by dschuessler 1869 days ago
I agree with both of your statements. They are definitely important points to make about your observation. But your post seems to argue against Martin's standpoint and for the assertion that „Tests are not specifications.“

From the fact that there are some tests out there that are barely specifying anything, it does neither follow that tests are not supposed to be specifications nor that tests are not specifications in general.

I think these are important distinctions to make.

1 comments

When you read the entire section of the book, Martin claims that those tests main purpose is to serve as a normative documentation. The developer can read the test case and then figure out what was meant to be programmed.

While it might be illuminating in some cases, it might be not helpful or either misleading in other cases.

It's like arguing that the main purpose of magazines is to lit a fire with them, because some of them are very flammable.

Tests are good to ensure that some property of the system that held true before still holds true after some modifications to the system has been made.