3 ms·
This article goes on about "why traditional testing is not sufficient". I think their view of 'traditional testing' is a strawman. Traditional testing never sa
by eesmith 7y ago
This article goes on about "why traditional testing is not sufficient". I think their view of 'traditional testing' is a strawman.
Traditional testing never said that 100% code testing was sufficient.
Even 100% branch testing isn't sufficient. SQLite gets bug reports (eg, through fuzzing) even though they have some of the highest covered code ever.
Viktor Fracic's comment “Code coverage means nothing" is the traditional view on coverage. Code coverage only means something when you are testing so that code coverage can help. Otherwise, it's easy to get high coverage with meaningness tests.
And that's been the view of code coverage for a very long time.
Ditto for "High quality testing takes time and doesn’t guarantee success." Has anyone ever said that high-quality testing guarantees success? Perhaps a few odd-balls, but it's never been the majority view.
"I’d rather see people move fast and be comfortable with failing" depends very much on your market. (Boeing avionics, ahem.)
In other words, testing has never been sufficient. Only necessary.
- grayed-down 7y agoGreat response! I read the headline and asked myself what the hell else is there to do? Get a papal blessing and/or a good law firm, what?