common-java:DuplicatedBlocks

Source files should not have any duplicated blocks

Bad Coding Practices - (1006)

common-java:SkippedUnitTests

Skipped unit tests should be either removed or fixed

Bad Coding Practices - (1006)

common-java:InsufficientBranchCoverage

Branches should have sufficient coverage by tests

Bad Coding Practices - (1006)

common-java:InsufficientCommentDensity

Source files should have a sufficient density of comment lines

Bad Coding Practices - (1006)

common-java:InsufficientLineCoverage

Lines should have sufficient coverage by tests

Bad Coding Practices - (1006)

Classes and enums with private members should have a constructor

Permission Issues - (275)

Boolean expressions should not be gratuitous

Expression Issues - (569)

Lambdas should not have too many lines

Bad Coding Practices - (1006)

Consecutive AssertJ "assertThat" statements should be chained

Bad Coding Practices - (1006)

Regexes containing characters subject to normalization should use the CANON_EQ flag

Bad Coding Practices - (1006)

Track uses of "TODO" tags

Bad Coding Practices - (1006)

"default" clauses should be last

Bad Coding Practices - (1006)

Similar tests should be grouped in a single Parameterized test

Bad Coding Practices - (1006)

Tests should use fixed data instead of randomized data

Bad Coding Practices - (1006)

Strings literals should be placed on the left side when checking for equality

Deprecated code should be removed

Bad Coding Practices - (1006)

Track uses of "FIXME" tags

Bad Coding Practices - (1006)

"Exception" should not be caught when not required by called methods

Error Conditions, Return Values, Status Codes - (389)

Spring's ModelAndViewAssert assertions should be used instead of other assertions

Bad Coding Practices - (1006)

"Optional" should not be used for parameters

Data Processing Errors - (19)

Tests should be stable

Bad Coding Practices - (1006)

"throws" declarations should not be superfluous

Error Conditions, Return Values, Status Codes - (389)

Value-based objects should not be serialized

Bad Coding Practices - (1006)

Character classes should be preferred over reluctant quantifiers in regular expressions

Expression Issues - (569)

Track uses of disallowed classes

Bad Coding Practices - (1006)

"@Deprecated" code marked for removal should never be used

API / Function Errors - (1228)

Limited dependence should be placed on operator precedence

Behavioral Problems - (438)

Exit methods should not be called

Bad Coding Practices - (1006)

Whitespace and control characters in literals should be explicit

Data Processing Errors - (19)

Unicode-aware versions of character classes should be preferred

Data Processing Errors - (19)

Parameters should be passed in the correct order

Data Processing Errors - (19)

IllegalMonitorStateException should not be caught

Bad Coding Practices - (1006)

Unused "private" methods should be removed

Permission Issues - (275)

"ResultSet.isLast()" should not be used

API / Function Errors - (1228)

A "while" loop should be used instead of a "for" loop

Behavioral Problems - (438)

"URL.hashCode" and "URL.equals" should be avoided

Bad Coding Practices - (1006)

Names of regular expressions named groups should be used

Expression Issues - (569)

Try-catch blocks should not be nested

Error Conditions, Return Values, Status Codes - (389)

Methods should not have too many return statements

Bad Coding Practices - (1006)

Increment (++) and decrement (--) operators should not be used in a method call or mixed with other operators in an expression

Bad Coding Practices - (1006)

Synchronized classes Vector, Hashtable, Stack and StringBuffer should not be used

Bad Coding Practices - (1006)

Character classes in regular expressions should not contain the same character twice

Expression Issues - (569)

Package declaration should match source file directory

Bad Coding Practices - (1006)

"collect" should be used with "Streams" instead of "list::add"

File Handling Issues - (1219)

"private" and "final" methods that don't access instance data should be "static"

Permission Issues - (275)

Cognitive Complexity of methods should not be too high

Complexity Issues - (1226)

The Object.finalize() method should not be overridden

Bad Coding Practices - (1006)

Tests should be kept in a dedicated source directory

Bad Coding Practices - (1006)

"Collections.EMPTY_LIST", "EMPTY_MAP", and "EMPTY_SET" should not be used

Bad Coding Practices - (1006)

Lazy initialization of "static" fields should be "synchronized"

Initialization and Cleanup Errors - (452)

Track uses of "NOSONAR" comments

Bad Coding Practices - (1006)

Redundant pairs of parentheses should be removed

Bad Coding Practices - (1006)

Labels should not be used

Bad Coding Practices - (1006)

"static" members should be accessed statically

Permission Issues - (275)

Classes with only "static" methods should not be instantiated

Permission Issues - (275)

"Lock" objects should not be "synchronized"

Resource Locking Problems - (411)

Multiline blocks should be enclosed in curly braces

Behavioral Problems - (438)

Local variables should not shadow class fields

Bad Coding Practices - (1006)

Utility classes should not have public constructors

Permission Issues - (275)

Wildcard imports should not be used

API / Function Errors - (1228)

Unused type parameters should be removed

Bad Coding Practices - (1006)

Assertion arguments should be passed in the correct order

Bad Coding Practices - (1006)

Chained AssertJ assertions should be simplified to the corresponding dedicated assertion

Bad Coding Practices - (1006)

Empty statements should be removed

Bad Coding Practices - (1006)

"switch" statements should not have too many "case" clauses

Bad Coding Practices - (1006)

Null should not be returned from a "Boolean" method

Pointer Issues - (465)

Loggers should be named for their enclosing classes

Audit / Logging Errors - (1210)

Unit tests should throw exceptions

Error Conditions, Return Values, Status Codes - (389)

AssertJ "assertThatThrownBy" should not be used alone

Error Conditions, Return Values, Status Codes - (389)

Return of boolean expressions should not be wrapped into an "if-then-else" statement

Expression Issues - (569)

Test assertions should include messages

Bad Coding Practices - (1006)

Regular expressions should not be too complicated

Expression Issues - (569)

Boolean literals should not be redundant

Bad Coding Practices - (1006)

Local variables should not be declared and then immediately returned or thrown

Bad Coding Practices - (1006)

Tests should include assertions

Bad Coding Practices - (1006)

String offset-based methods should be preferred for finding substrings from offsets

Bad Coding Practices - (1006)

Assignments should not be made from within sub-expressions

Expression Issues - (569)

Deprecated elements should have both the annotation and the Javadoc tag

Documentation Issues - (1225)

Modifiers should be declared in the correct order

Bad Coding Practices - (1006)

Types should be used in lambdas

Redundant modifiers should not be used

Bad Coding Practices - (1006)

Inner classes which do not reference their owning classes should be "static"

Permission Issues - (275)

Instance methods should not write to "static" fields

Permission Issues - (275)

Source code should be indented consistently

Bad Coding Practices - (1006)

Unnecessary imports should be removed

Bad Coding Practices - (1006)

"indexOf" checks should not be for positive numbers

Pointer Issues - (465)

Threads should not be started in constructors

Concurrency Issues - (557)

Empty lines should not be tested with regex MULTILINE flag

Bad Coding Practices - (1006)

Test methods should not contain too many assertions

Bad Coding Practices - (1006)

Factory method injection should be used in "@Configuration" classes

Data Neutralization Issues - (137)

Unused local variables should be removed

Bad Coding Practices - (1006)

Underscores should be used to make large numbers readable

Bad Coding Practices - (1006)

Ternary operators should not be nested

Expression Issues - (569)

'List.remove()' should not be used in ascending 'for' loops

Behavioral Problems - (438)

Exception testing via JUnit ExpectedException rule should not be mixed with other assertions

Error Conditions, Return Values, Status Codes - (389)

Exception testing via JUnit @Test annotation should be avoided

Error Conditions, Return Values, Status Codes - (389)

Mocking all non-private methods of a class should be avoided

Permission Issues - (275)

Public types, methods and fields (API) should be documented with Javadoc

Documentation Issues - (1225)

Catches should be combined

Error Conditions, Return Values, Status Codes - (389)