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

        Test class names should end with "Test"

        consistency - identifiable
        maintainability
        Code Smell
        • tests
        • phpunit

        Why is this an issue?

        How can I fix it?

        More Info

        For better organization and clarity in test suites, test classes should end with *Test.php. This naming convention helps to easily identify and distinguish test classes from other classes in the codebase. It allows for automated test runners or frameworks to locate and execute the tests systematically.

        The PHPUnit command-line test runner will look for *Test.php files. In that case, test files without this pattern are ignored and not executed without warning.

        What is the potential impact?

        When tests are ignored or skipped, there can be several negative impacts on the development process and code quality.

        Firstly, ignoring tests can lead to undetected bugs and vulnerabilities, as the skipped tests are not being executed and their associated functionality is not being thoroughly tested. This increases the risk of releasing software with undiscovered issues.

        Furthermore, skipped tests can result in a false sense of confidence, as developers might assume that the code is functioning correctly without proper validation.

        This can lead to regression issues or unexpected behavior in the future when changes are made to the codebase.

          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