Let's celebrate: Unit Tests

[tig]

Back before we launched 1.0, the code coverage for unit tests was in the 30-40% range IIRC.

I just checked the latest Fine Code Coverage results and:

There's no way of knowing when "enough is enough for unit tests for a project; there's no perfect # and (IMO) setting goals is a bad idea because it can drive bad behavior (people gaming things just to reach the goal).

But getting contributors to agree to investing in automated unit tests is a very important cultural change for a project and when there's clear evidence the quality of the project has improved as a result, such work should be celebrated.

So....

NICE WORK TEAM! ;-)

Keep it up.

[tig]

I have no idea whether using Cyclomatic Complexity is really a good test of whether more unit tests are needed or not, but the fact that FCC uses it to indicate risk areas makes me want to share this:

We have a tracking issue for figuring out how to build more tests for the drivers: #1316

What else can we do to gain more confidence in the components FCC lists as risk areas?