Patrick Smacchia has recently announced NDepend 5.0, the latest version of his .NET code analyzer coming with a number of enhancements: support for VS 2013, trend monitoring, new dashboard and a major UI facelift.
False confidence is often grounded in wishful thinking. It is defined as a state where the projected reality and the actual reality might differ considerably, however for a limited period of time, it does give a feeling of having everything under control. There are many such situations in Agile development which make a team hold onto the false confidence crutch only to fall later.
Adobe has made available a prerelease of an ActionScript Code Coverage Plug-in for Flash Builder, which aims to help developers understand exactly what code is executed while an application is running. When added to Flash Builder, the plug-in provides a new Eclipse perspective that allows you to start the code coverage tool.
NDepend 3.0 comes integrated with Visual Studio analyzing code in real time, can analyze code over multiple VS solutions, supports editing of multiple CQL rules at one time, and comes with enhanced search and performance.
The recent release of Clover 2.4 highlights a new "Test Optimization" feature that offers to speed up CI builds and allow developers to spend less time waiting for their tests to run. The feature leverages "per-test" coverage data to selectively run only the tests impacted by your code changes.
Christian Gruber takes some time to clarify the TDD stance on using code coverage metrics. He discusses what code coverage metrics do and don't tell you, how TDD fits into the picture, and how one might be best advised to use their code coverage metrics.
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.
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.
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 is beginning to fill the void left by NCover. Both SharpDevelop and TreeSurgeon have integrated PartCover to provide code coverage.
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.
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.
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.
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.