InfoQ Homepage Code Coverage Content on InfoQ
-
Coverity Readiness Manager Brings Quick Visibility to Code Characteristics
Coverity recently released Readiness Manager for Java providing a dashboard and analysis for code complexity, violation of best practices, architectural integrity, interdependencies, and test coverage.
-
Getting Up-to-Speed on NDepend and Code Metrics
Any tool is only good if it is in the hands of a developer who knows how to use it. NDepend is one of those tools which is very powerful but addresses an aspect of software development too few architects or developers understand, software metrics.
-
Cyclomatic Complexity Revisited
Enerjy studied tens of thousands of source code files and found the optimum Cyclomatic Complexity number is 11, with a 28% defect probability. In fact, you are more likely to encounter a defect if you have lower complexity - is it time to make your methods are more complicated?
-
PartCover: New Open Source Code Coverage Tool
PartCover is beginning to fill the void left by NCover. Both SharpDevelop and TreeSurgeon have integrated PartCover to provide code coverage.
-
Debuggers considered Harmful?
A blog post titled "Debugger Support Considered Harmful" claims that Ruby debugging support is lacking - and that that's a good thing. We look at the various rebuttals and the state of Ruby debuggers.
-
Google SoC Series: dcov - Ruby documentation coverage analyzer
Ruby gains another tool to ensure code quality: dcov analyses Ruby code and determines the documentation coverage. We caught up with dcov developer Jeremy McAnally to talk about his plans.
-
100% Test Coverage?
How much testing is enough? The answer varies depending on whom you ask. On one end of the spectrum, some say you should strive to achieve 100% test coverage. Others say it doesn't matter, that you should just rely on the quality of the tests, and that measuring test coverage does not tell you anything about the quality of the tests and the code being tested.
-
Heckle Your Way to Better Tests
Like Jester, the Java program that inspired it, Heckle mutates your Ruby code, attempting to make your unit tests fail. The premise is simple: If your unit test doesn't choke on Heckle's mutated code, then you need to improve coverage.