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
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
C#

C# static code analysis

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

  • All rules 493
  • Vulnerability46
  • Bug88
  • Security Hotspot24
  • Code Smell335

  • Quick Fix 61
Filtered: 9 rules found
tests
    Impact
      Clean code attribute
        1. Test method signatures should be correct

           Code Smell
        2. "[ExpectedException]" should not be used

           Code Smell
        3. Assertion arguments should be passed in the correct order

           Code Smell
        4. Assertions should be complete

           Code Smell
        5. "Thread.Sleep" should not be used in tests

           Code Smell
        6. Literal boolean values should not be used in assertions

           Code Smell
        7. Tests should include assertions

           Code Smell
        8. Test classes should contain at least one test case

           Code Smell
        9. Tests should not be ignored

           Code Smell

        Test method signatures should be correct

        intentionality - logical
        maintainability
        Code Smell
        • tests

        Why is this an issue?

        More Info

        A method is identified as a test method if it is marked with one of the following attributes:

        • [TestMethod] or [DataTestMethod] (for MSTest).
        • [Fact] or [Theory] (for xUnit).
        • [Test], [TestCase], [TestCaseSource], or [Theory] (for NUnit).

        However, non-public methods are not considered test methods and will not be executed, regardless of whether they have a test attribute. Additionally, methods with the async void modifier or methods that contain generics <T> anywhere in their signatures are also excluded from being recognized as tests and will not be executed.

        [TestMethod]
        void TestNullArg()  // Noncompliant, method is not public
        {  /* ... */  }
        
        [TestMethod]
        public async void MyIgnoredTestMethod()  // Noncompliant, this is an 'async void' method
        { /* ... */ }
        
        [TestMethod]
        public void MyIgnoredGenericTestMethod<T>(T foo)  // Noncompliant, method has generics in its signature
        { /* ... */ }
        
        [TestMethod]
        public void TestNullArg()
        {  /* ... */  }
        
        [TestMethod]
        public async Task MyIgnoredTestMethod()
        { /* ... */ }
        
        [TestMethod]
        public void MyIgnoredGenericTestMethod(int foo)
        { /* ... */ }
        

        Exceptions

        For xUnit, accessibility is disregarded when it comes to [Fact] test methods, as they do not necessarily need to be declared as public.

        In xUnit, [Theory] test methods, as well as [TestCase] and [TestCaseSource] test methods in NUnit, have the flexibility to be generic, allowing for a wider range of test scenarios.

          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