code review

Reviewers read the code line by line to check for:

• Flaws or potential flaws
• Consistency with the overall program design
• The quality of comments
• Adherence to coding standards.

Code review may be especially productive for identifying security vulnerabilities. Specialized application programs are available that can help with this process. Automated code reviewing facilitates systematic testing of source code for potential trouble such as buffer overflows, race conditions, memory leakage, size violations, and duplicate statements. Code review is also commonly done to test the quality of patches.

Read more about code review: - Mozilla.org answers frequently asked questions (FAQ) about code review. - PMD is a program that scans Java source code and looks for problems. - Checkstyle is another popular Java code review program.

Do you have something to add to this definition? Let us know. Send your comments to techterms@whatis.com

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Testing software in the dark is problematic Testing late in development and without software artifacts such as the design, architecture and code, makes it difficult to catch and repair bugs and... Software testers: Identity crisis or delusions of grandeur? Without a clear understanding of what software testers do, people try to interpret what they do from their job title. The problem is the many... Determining the testing organization's place within a company Software testing organizations are a vital part of the SDLC, but where does testing fit within a company? Mike Kelly and Rob Apmann offer advice on...

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary auditor  (SearchSoftwareQuality.com) build  (SearchSoftwareQuality.com) In a programming context, a build is a version of a program.