SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
Java

Java static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your JAVA code

  • All rules 733
  • Vulnerability60
  • Bug175
  • Security Hotspot40
  • Code Smell458

  • Quick Fix 65
Filtered: 24 rules found
unused
    Impact
      Clean code attribute
        1. Types of unused record components should be removed from pattern matching

           Code Smell
        2. Packages containing only "package-info.java" should be removed

           Code Smell
        3. Collection contents should be used

           Code Smell
        4. Unused "private" classes should be removed

           Code Smell
        5. JUnit rules should be used

           Code Smell
        6. "catch" clauses should do more than rethrow

           Code Smell
        7. Conditionally executed code should be reachable

           Bug
        8. Unused type parameters should be removed

           Code Smell
        9. Files should not be empty

           Code Smell
        10. TestCases should contain tests

           Code Smell
        11. Unnecessary equality checks should not be made

           Bug
        12. Values should not be uselessly incremented

           Bug
        13. Fields in non-serializable classes should not be "transient"

           Code Smell
        14. Related "if/else if" statements should not have the same condition

           Bug
        15. Unused assignments should be removed

           Code Smell
        16. Unused local variables should be removed

           Code Smell
        17. Sections of code should not be commented out

           Code Smell
        18. Unused method parameters should be removed

           Code Smell
        19. Unused "private" methods should be removed

           Code Smell
        20. Exceptions in "throws" clauses should not be superfluous

           Code Smell
        21. Unnecessary imports should be removed

           Code Smell
        22. Empty statements should be removed

           Code Smell
        23. Unused "private" fields should be removed

           Code Smell
        24. Unused labels should be removed

           Code Smell

        JUnit rules should be used

        intentionality - clear
        maintainability
        Code Smell
        • junit
        • tests
        • unused

        Why is this an issue?

        How can I fix it?

        More Info

        JUnit rules are predefined classes that extend the behavior of JUnit tests, allowing to add new functionalities, such as managing resources, modifying test behavior, and handling exceptions.

        Unused JUnit rules can lead to confusion when reading the test code, making tests harder to understand and maintain. Having unused rules can also slow down the test suite, as JUnit has to process the rules even though they are not being used. Some TestRule classes have the desired effect without being directly referenced by a test, while others do not. There’s no reason to leave them cluttering the file if they’re not in use.

        The rule raises an issue when in a Test class, there is no method referencing a declared TestRule of the following types:

        • TemporaryFolder and TestName in JUnit
        • TempDir and TestInfo in JUnit 5
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube Community BuildAnalyze code in your
          on-premise CI
          Available Since
          9.1
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use