Scribd
Upload
32 views1 page

Code Review Checklist: Name of Reviewer: Name of Coder: File(s) Under Review: Brief Description of Change Being Reviewed

This document provides a checklist for reviewing code that includes checking for adherence to coding standards and guidelines, proper commenting practices, logical accuracy, error handling, and optimal code design decisions. The reviewer uses this checklist to evaluate code changes by examining indentation, naming, spacing, unnecessary comments, edge cases, abstraction level, and other factors to ensure high quality code.

Uploaded by

anarki85
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
32 views1 page

Code Review Checklist: Name of Reviewer: Name of Coder: File(s) Under Review: Brief Description of Change Being Reviewed

This document provides a checklist for reviewing code that includes checking for adherence to coding standards and guidelines, proper commenting practices, logical accuracy, error handling, and optimal code design decisions. The reviewer uses this checklist to evaluate code changes by examining indentation, naming, spacing, unnecessary comments, edge cases, abstraction level, and other factors to ensure high quality code.

Uploaded by

anarki85
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Code Review Checklist

Coding Standards Review Information:


 understandable
Name of Reviewer:
 adhere code guidelines
 indentation Name of Coder:
 no magic numbers
 naming
File(s) under review:
 units, bounds Brief description of change being reviewed:
 spacing: horizontal (btwn
operators, keywords) and
vertical (btwn methods, blocks)
Comments
 no needless comments Review Notes (problems or decisions):
 no obsolete comments
 no redundant comments
 methods document parameters
it modifies, functional
dependencies
 comments consistent in format,
length, level of detail
 no code commented out
Logic
 array indexes within bounds
 conditions correct in ifs, loops
 loops always terminate
 division by zero
 refactor statements in the loop
to outside the loop
Error Handling
 error messages understandable
and complete
 edge cases (null, 0, negative)
 parameters valid
 files, other input data valid
Code Decisions
 code at right level of
abstraction
 methods have appropriate
number, types of parameters
 no unnecessary features
 redundancy minimized
 mutability minimized
 static preferred over nonstatic
 appropriate accessibility
(public, private, etc.)
 enums, not int constants
 defensive copies when needed
 no unnecessary new objects
 variables in lowest scope
 objects referred to by their
interfaces, most generic SVN Versions (if applicable):
supertype Before review:
After revisions:

You might also like