Code review automates the process of checking code for bugs and adherence to best practices. It is quick and easy to run, allowing developers and architects to find problems early when they are easy to fix.

Image of the code review window in the workspace.



For each issue it identifies, code review explains the problem...

Image of the Code Review Details window, Description tab.



...then shows an example of problem code...

Image of the Code Review Details window, Examples tab.



...and then offers a recommendation. In some cases, code review can automatically fix the problem.

Image of the Code Review Details window, Solutions tab.



Several code reviews are supplied, each containing sets of rules. You can choose to run particular code reviews at any stage, or run all of them.

Image of the code review preferences window.



You also can create rules. New rules can be architectural controls or general rules.

Image of the New Rule window.



There are three severity levels: Problem, Warning, and Recommendation.

Image of the three severity level icons.



Problem is the highest level, and represents problems that must be fixed.

Image of the Problem severity icon.



Warning means a potential problem that should be addressed.

Image of the Warning severity icon.



Recommendation is the lowest level, but these problems should not be overlooked. Addressing them likely will prevent larger problems in the future.

Image of the Recommendation severity icon.



If a quick fix is available, it is indicated by one of these icons.

Image of the three quick fix icons.



This demonstration shows a developer importing files into a new Java project, running a code review, and applying a quick fix.

Image of a quick fix being applied.
No image.

This concludes the tour. To learn more, refer to the Tutorial Gallery for a tutorial on running a code review, or refer to the Information Center.