Home ›
More executable paths through code correlates with higher likelihood of bugsMore executable paths through code correlates with higher likelihood of bugs
Submitted by Benjamin Melançon on October 1, 2011 - 11:27pm
Searched words:
code quality metrics measuring complexity
The McCabe Cyclomatic Complexity metric (which counts the number of different executable paths through a module) proves to be an excellent measure of code quality. The more paths through a program, the more complicated it is, and the more bugs the program is likely to have.
http://www.enerjy.com/blog/?p=198
if we know nothing else about a file except that it has a high Cyclomatic Complexity value, we can now have more reason to believe that it is likely to cause problems (keeping in mind of course that there are no guarantees about anything in this life).
More like this
- Created a View through the wizard... page not found going to its path
- JavaScript Bookmarklet to open a web site's path in a new window with a different base URL
- How to create a Feature without the initial download through the UI
- Check for duplicate titles of a node with AJAX to warn immediately before entering more data or submitting
- Michigan CEO: Soul-Crushing Sprawl Killing Business | Rust Wire
Comments
We’re very excited to get to
We’re very excited to get to the point in the project where we can provide a pre-release version of Windows 8 that is broadly usable by the tech community on a daily basis. We know folks who are anxious to run the Microsoft Windows 8 Consumer Preview are probably interested in suggestions around what hardware to use. This post provides the technical details behind system recommendations.
Post new comment