Patrick Smacchia [MVP C#]

How to avoid regression bugs while adding new features

I recently published an article on SearchWinDeveloment. It explains how we (the NDepend team) are using NDepend to analyze the NDepend code to avoid regression bugs while adding new features.

More specifically, we are using the possibility to compare 2 versions of our code base. Then we focus our efforts on reviewing and testing the code that has been modified or that was added since the last release. My experience always showed that the bulk of problems come from fresh code.

Of course, the preferred way to avoid regression bug is to have a high automatic test coverage ratio on the new code but it is rarely possible to have 100% coverage, especially on application with a complex UI.

Published Dec 20 2007, 07:57 PM by Patrick Smacchia

Comments

» Daily Bits - December 21, 2007 (Early Edition) Alvin Ashcraft’s Daily Geek Bits: Daily links plus random ramblings about development, gadgets and raising rugrats. said:

Pingback from » Daily Bits - December 21, 2007 (Early Edition) Alvin Ashcraft’s Daily Geek Bits: Daily links plus random ramblings about development, gadgets and raising rugrats.

# December 20, 2007 7:59 PM

Name (required)

Your URL (optional)

Comments (required)

Remember Me?

Enter the numbers above:

Add

About Patrick Smacchia

Patrick Smacchia is a Visual C# MVP involved in software development for over 15 years. After graduating in mathematics and computer science, he has worked on software in a variety of fields including stock exchange, airline ticket reservation system as well as a satellite base station at Alcatel. He's currently a software consultant and trainer on .NET technologies as well as the lead developer of the tool NDepend which provides numerous metrics and caveats on any compiled .NET application. He is the author of Practical .NET2 and C#2, a .NET book conceived from real world experience with 647 compilable code listings.