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: 7 rules found
assertj
    Impact
      Clean code attribute
        1. AssertJ "assertThatThrownBy" should not be used alone

           Code Smell
        2. Consecutive AssertJ "assertThat" statements should be chained

           Code Smell
        3. AssertJ assertions "allMatch" and "doesNotContain" should also test for emptiness

           Bug
        4. Chained AssertJ assertions should be simplified to the corresponding dedicated assertion

           Code Smell
        5. AssertJ methods setting the assertion context should come before an assertion

           Bug
        6. AssertJ configuration should be applied

           Bug
        7. Assertions should be complete

           Code Smell

        AssertJ "assertThatThrownBy" should not be used alone

        adaptability - tested
        maintainability
        Code Smell
        • tests
        • assertj

        Why is this an issue?

        Unlike similar AssertJ methods testing exceptions (assertThatCode(), assertThatExceptionOfType(), …​), the assertThatThrownBy() method can be used alone, failing if the code did not raise any exception.

        Still, only testing that an exception was raised is not enough to guarantee that it was the expected one, and you should test the exception type or content further. In addition, it will make explicit what you are expecting, without relying on side-effects.

        This rule raises an issue when assertThatThrownBy is used, without testing the exception further.

        Noncompliant code example

        assertThatThrownBy(() -> shouldThrow()); // Noncompliant, is it really the exception you expected?
        

        Compliant solution

        assertThatThrownBy(() -> shouldThrow()).isInstanceOf(IOException.class);
        //or
        assertThatThrownBy(() -> shouldThrow()).hasMessage("My exception");
        
          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