Quality Matters

14 October 2015

Unit tests take too much time to write and are not necessary. Automated test infrastructure is costly to create and maintain. We don’t need a complete approach to quality because it’s expensive. What’s that QA item in the quote? We’ll just have everyone run through it before we release.
 
Tell that to this company, which got hit with an $8 million bill from the SEC, including a $5 million fine. This was due in part to some complex code that was deleted by a developer that didn’t understand it. Good unit tests should have caught this (and even prevented it in the first place as the test would serve as documentation for the complex code). This is pretty extreme, but definitely an example of why quality matters. Even if your company isn’t engaging in millions of dollars of business in a highly regulated environment, I would say that there can be real costs to poor quality and the measures to counter it really aren’t that hard or expensive in the end.


comments powered by Disqus