3 ms·

You can't assert everything, you can't test everything (like the tests themselves). You can't assert a list of hard coded values are all correctly spelled via

You can't assert everything, you can't test everything (like the tests themselves). You can't assert a list of hard coded values are all correctly spelled via an assert. You can't determine if a library that has it's own asserts is failing or your code is failing. You can't always add asserts to legacy code, etc.

gouranga 14y ago
And? I fail to see your point. Assertions check assumptions and tests test code. And yea you can use a dictfile from Unix to test spelling quite easily (we do it for document construction) Nothing is ever 100% certain. Are you suggesting that I magically write perfect software? I don't, but it works first time in 99% of cases with the right tests and assertions. The 1% left goes to debugging. Our bug rate is approx 1 per 2000 lines of code that hit production.