How to measure the benefits of unit testing?

Question

I am trying to push my company to conduct unit tests as part of the development cycle. I got a testing framework that works with our MVC framework, and several team members are now writing unit tests. However, I am where I need to do this in order to improve our hourly assembly, the ease of figuring out what fixtures you need, adding functionality to the mock-up generator, etc. Etc., And I want to be able to make a case for this work a guide. In addition, I would like us to take the time to write unit tests for the most important parts of the existing code, and I just don’t see it happening without a more specific case than “everyone knows that unit tests are good.”

How do you assess the positive impact of (comprehensive and reliable) unit tests on your projects? I can, of course, look at the number and severity of errors that have been filed and compared with our increase in code coverage, but this is a rather weak metric.

Answer 1

Sonar is a company that makes a very interesting code verification tool, they are actually trying to measure technical debt , which compares unverified code and the price per developer per hour.

Answer 2

Quantifying test quality is very difficult.

. 100% - - (, ). -, .

, , - . . , ( ).

:

• , ( )?
• , , (, , , unit test)