News for hackers. Stuff that matters.
Re:The tragedy of 100% code coverage (2016) by thehardsphere on Wednesday May 10, 2017 @04:21PM (#14311288)
Well, if the organization tracks the time developers spend doing things, then it should be easy to estimate the waste.

1. Take the number of hours spent writing tests.

2. Multiply by whatever percentage of the tests are unnecessary.

3. Multiply by the labor cost per hour. Or revenue that was not made (e.g. if you could have billed those hours to a customer, but didn't).

The resulting number could either be a big deal or not, depending on how big your organization is and how much time you spent on superfluous tests.

There are no comments on this comment yet.