News for hackers. Stuff that matters.
Re:Why Most Unit Testing is Waste [pdf] by sehugg on Thursday March 06, 2014 @10:32AM (#7354245)
• Keep regression tests around for up to a year — but most of those will be system-level tests rather than unit tests.

• Keep unit tests that test key algorithms for which there is a broad, formal, independent oracle of correctness, and for which there is ascribable business value.

• Except for the preceding case, if X has business value and you can text X with either a system test or a unit test, use a system test — context is everything.

• Design a test with more care than you design the code.

• Turn most unit tests into assertions.

• Throw away tests that haven’t failed in a year.

• Testing can’t replace good development: a high test failure rate suggests you should shorten development intervals, perhaps radically, and make sure your architecture and design regimens have teeth

• If you find that individual functions being tested are trivial, double-check the way you incentivize developers’ performance. Rewarding coverage or other meaningless metrics can lead to rapid architecture decay.

• Be humble about what tests can achieve. Tests don’t improve quality: developers do

Re:Why Most Unit Testing is Waste [pdf] by TwoBit on Thursday March 06, 2014 @04:56PM (#7356895)

   >> Throw away tests that haven’t failed in a year.
That's absolutely f*ing crazy. Throwing those tests away makes it impossible for me to know that any changes I make to the implementation are OK.
Re:Why Most Unit Testing is Waste [pdf] by mempko on Thursday March 06, 2014 @08:11PM (#7357822)
Why? Don't you use assertions?
Re:Why Most Unit Testing is Waste [pdf] by smtddr on Thursday March 06, 2014 @08:40PM (#7357941)
No amount of assertions in production code can replace assertions of unit-tests; assuming the unittests are designed to try all known common & edge cases.
Re:Why Most Unit Testing is Waste [pdf] by TwoBit on Friday March 07, 2014 @03:47AM (#7359132)
Also, assertions only flag code that gets executed when you test it. Unless you can be sure that you have tested every possible execution possibility before shipping, you cannot know if after shipping your code will execute something that you missed during testing. This happens a lot.

Additionally, the unit tests allow me to safely maintain the code from the comfort of my own desk. If I relied only on assertions then I would literally have to send changes to all possible users and ask each of them to please test and tell me if they got any assertions. And do this for me three times a week for the next two years.

Re:Why Most Unit Testing is Waste [pdf] by mempko on Friday March 07, 2014 @09:08AM (#7360233)
Who said only?
Re:Why Most Unit Testing is Waste [pdf] by Wohui on Thursday March 06, 2014 @02:01PM (#7355817)
Beautiful.
Re:Why Most Unit Testing is Waste [pdf] by jmnicolas on Thursday March 06, 2014 @12:40PM (#7355234)
Thanks.