Re:Questions to ask yourself when writing tests
by newfoundglory on Tuesday January 02, 2018 @04:28PM
(#16055874)
I disagree and am horrified by the dystopic image of our entire test suite having two possible results: "everything passed" or "something is wrong".
[ Parent
| on HN ]
Re:Questions to ask yourself when writing tests
by arkh on Tuesday January 02, 2018 @06:03PM
(#16056716)
Not two results.
But "when you click on this after that this happen while it shouldn't" is usually enough info to start debugging: you have reproducible steps. Which you can do with a debugger running so you see exactly were and how things break.
And it is a lot less brittle than "well we tried to refactor some minor thing and now everything is red; but we don't know if the software behavior changed or just because our tests were just checking the implementation".
Re:Questions to ask yourself when writing tests
by newfoundglory on Wednesday January 03, 2018 @03:52AM
(#16059500)
well, if you're determined to write stupid tests you can do it at any level. And that is not enough info to start debugging unless you had the machine in a known and reproducible state to begin with, which is where we get back to writing focused reproducible tests.