Java Code Quality Tools
Download as PPTX, PDF7 likes20,592 views
This document discusses several Java code quality tools, including CodeProAnalytix for code analysis and metrics, PMD for detecting bugs and suboptimal code, FindBugs for finding correctness bugs and bad practices, and Cobertura/EMMA for code coverage analysis. It also mentions Checkstyle for checking code against coding standards, Tattletale for dependency analysis, and consolidated tools like Sonar and Xradar. Finally, it describes UCDetector for finding unnecessary public code.
Java Code Quality Tools
- 1. Java Code Quality Toolsby OrestIvasivTwitter: @halyphBlog: halyph.blogspot.com
- 2. CodeProAnalytixCode AnalysisMetricsCode Coverage Dependency AnalysisJUnit Test GenerationSimilar Code Analysis
- 3. PMDPossible bugs - empty try/catch/finally/switch statementsDead code - unused local variables, parameters and private methodsSuboptimal code - wasteful String/StringBuffer usageOvercomplicated expressions - unnecessary if statements, for loops that could be while loopsDuplicate code - copied/pasted code means copied/pasted bugs
- 4. FindBugsCorrectness bug - Probable bug - an apparent coding mistake resulting in code that was probably not what the developer intended. We strive for a low false positive rate. Bad Practice - Violations of recommended and essential coding practice. Examples include hash code and equals problems, cloneable idiom, dropped exceptions, serializable problems, and misuse of finalize. We strive to make this analysis accurate, although some groups may not care about some of the bad practices. Dodgy - Code that is confusing, anomalous, or written in a way that leads itself to errors. Examples include dead local stores, switch fall through, unconfirmed casts, and redundant null check of value known to be null. More false positives accepted. In previous versions of FindBugs, this category was known as Style.
- 5. Code CoverageCoberturaeCobertura – Eclipse PluginEMMAEclEmma and JaCoCo – Eclipse Plugins
- 6. Coding standard analysisCheckstyle is a development tool to help programmers write Java code that adheres to a coding standard. It automates the process of checking Java code to spare humans of this boring (but important) task. This makes it ideal for projects that want to enforce a coding standard.
- 7. TattletaleIdentify dependencies between JAR filesFind missing classes from the classpathSpot if a class/package is located in multiple JAR filesSpot if the same JAR file is located in multiple locationsWith a list of what each JAR file requires and providesVerify the SerialVersionUID of a classFind similar JAR files that have different version numbersFind JAR files without a version numberFind unused JAR archivesIdentify sealed / signed JAR archivesLocate a class in a JAR fileGet the OSGi status of your projectRemove black listed API usage
- 9. UCDetectorUnnecessary Code Detector is a eclipse PlugInto find unnecessary (dead) public Java code. For example public classes, methods or fields which have no references. UCDetector creates markers for the following problems, which appear in the eclipse problem view:Unnecessary (dead) codeCode where the visibility could be changed to protected, default or privateMethods of fields, which can be final