2 ms·
I mostly agree with you, although I think having a "score" can be really useful. It is only as useful as the underlying formula for calculating it, however. I
by freedomben 6y ago
I mostly agree with you, although I think having a "score" can be really useful. It is only as useful as the underlying formula for calculating it, however.
I view it like I do code coverage: it doesn't mean your code is well tested just because it has 100% coverage, but if the number is going down with each commit then that does likely indicate that testing is not a priority and isn't happening with regularity. The real problem comes in when people (especially managers) assume there is qualitative information inherent in the score, when there is not, or that it is a quantitative measure of test quality, when it is not.