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
PHP

PHP static code analysis

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

  • All rules 273
  • Vulnerability42
  • Bug51
  • Security Hotspot34
  • Code Smell146
Filtered: 13 rules found
tests
    Impact
      Clean code attribute
        1. Framework-provided functions should be used to test exceptions

           Code Smell
        2. Assertions should not be made at the end of blocks expecting an exception

           Bug
        3. Test methods should be discoverable

           Code Smell
        4. Assertions should not compare an object to itself

           Bug
        5. PHPUnit assertTrue/assertFalse should be simplified to the corresponding dedicated assertion

           Code Smell
        6. Only one method invocation is expected when testing exceptions

           Bug
        7. Assertion failure exceptions should not be ignored

           Bug
        8. Assertion arguments should be passed in the correct order

           Code Smell
        9. Test class names should end with "Test"

           Code Smell
        10. Literal boolean values and nulls should not be used in equality assertions

           Code Smell
        11. Tests should include assertions

           Code Smell
        12. TestCases should contain tests

           Code Smell
        13. A reason should be provided when skipping a test

           Code Smell

        A reason should be provided when skipping a test

        adaptability - tested
        maintainability
        Code Smell
        • tests
        • bad-practice
        • confusing
        • phpunit

        Why is this an issue?

        When a test fails due, for example, to infrastructure issues, you might want to ignore it temporarily. But without some kind of notation about why the test is being ignored, it may never be reactivated. Such tests are difficult to address without comprehensive knowledge of the project, and end up polluting their projects.

        This rule raises an issue on each test that is marked as incomplete or skipped without a message explaining the reasoning behind it.

        Noncompliant code example

        protected function setUp() {
          if (!extension_loaded('mysqli')) {
            $this->markTestSkipped(); // Noncompliant
          }
        }
        
        public function testSomething()
        {
          $this->assertTrue($result->isValid());
          $this->markTestIncomplete(); // Noncompliant
        }
        

        Compliant solution

        protected function setUp() {
          if (!extension_loaded('mysqli')) {
            $this->markTestSkipped( 'The MySQLi extension is not available.' ); // Compliant
          }
        }
        
        public function testSomething()
        {
          $this->assertTrue($result->isValid());
          $this->markTestIncomplete( 'Testing result validation is incomplete.' ); // Compliant
        }
        
          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