Two excellent code review tools：
1. CodePro http://code.google.com/javadevtools/codepro/doc/index.html
Key Features of 
| Dynamic, extensible tools that detect, report and repair deviations or non-compliance with predefined coding standards, popular frameworks, security and style conventions |  | Automated tools that measure and report on key quality indicators in a body of Java source code |  |
| Time-saving facility that uses sophisticated flow path analysis techniques to automates the creation of comprehensive JUnit regression tests |  | Powerful tools that measure what percentage of code is being executed using generated test cases or manual test scripts |  |
| A rich JUnit test editing environment that enables rapid creation, organization, modification and execution of unit tests. |  | Automated tools that analyze and visually depict the dependencies between projects, packages, and types |  |
| Efficiently examines Java code to find duplicate or very similar segments of code containing copy/paste bugs or that can be refactored to improve application design and maintainability |  | ||
2. Junipter http://code.google.com/p/jupiter-eclipse-plugin/
> Why you use the Jupiter rather than any other review tool?
Jupiter is:
open source - Jupiter follows the GNU License.
free - Jupiter is distributed free of charge.
IDE integration - Jupiter is based upon the Eclipse plug-in architecture.
Cross-platform - Jupiter is available for all platforms supported by Eclipse.
XML data storage - Jupiter stores data in XML format to simplify use and re-use.
CVS sharing - Jupiter shares individual review files in team via CVS.
Sorting and searching - Jupiter provides filters and sorting to facilitate issue review.
File integration - Jupiter supports jumping back and forth between reviews and source code.
> Junipter User Guide http://csdl.ics.hawaii.edu/techreports/03-11/03-11.html
扫一扫
128
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
