Re:Effective Code Reviews – A Primer
by asark on Thursday March 07, 2019 @11:55AM
(#19329633)
Do you trust any documentation at all? A test's just documentation a machine can read and, to some extent, validate. Other docs are necessarily even less trustworthy, if they can't be automatically checked for accuracy.
[ Parent
| on HN ]
Re:Effective Code Reviews – A Primer
by misterman0 on Thursday March 07, 2019 @12:05PM
(#19329736)
>>Do you trust any
The only test that matters to me is the one where a customer says "Yes, good!"
Sure, a test suite doesn't replace that. It helps ensure that test returns "Yes, good!", instead of "Why did you break this thing that worked last week!", assuming you know anything about what the customers consider good.
The parent sounds correct. One can have an extensive test suite and still turn out a product that is useless to the customer. These are 2 entirely separate concerns: testing is sanity checking that the code does what it is written to do, user validation is sanity checking that the code is actually useful to a customer (which most certainly cannot be automated or programmed).