London software testing news UK


Code inspection for bug detection

Posted in Software testing by testing in London on January 5, 2009

From Embedded.com

Fagan’s approach is in common use, though many groups tune it for their particular needs.

First, the objective of an inspection is to find bugs. Comments like “man, this code sucks!” are really attacks on the author and are inappropriate. Similarly, metrics one collects are not to be used to evaluate developers.

Secondly, all new code gets inspected. There are no exceptions. Teams that exclude certain types of routines because either they’re hard (“no one understands DMA here”) or because only one person really understands what’s going on will find excuses to skip inspections on other sorts of code, and will eventually give up inspections altogether.

We only inspect new code because there just isn’t time to pour over a million lines of stuff inherited in an acquisition.

Company testing software

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: