Please create a configuration option that allows to apply all sonar rules that are evaluated for src/main/java also to be applied to any code in src/test/java I think it is a common coding guideline that test code has to fulfill the same rules as production code.

Hey, Thanks for coming to us with this suggestion! You will be probably happy to learn that we are actually already working on the topic, as we also feel that quality and maintainability of tests is important… and it therefore should be nicely covered in SonarQube! We however realized that it woul…

Hi We are targeting java language and our workaround is to use the checkstyle maven plugin with all rules set to severity error which will break the CI build at least on any checkstyle issues. Any other code analysis depends if the user manually starts code inspection in IntelliJ for example. But t…

It is an interesting topic. I am very interested in see Sonar applying its features in testing too. It has a lot of sense for me. I am assuming in some time some plugin should be available to apply the best practices for JUnit 4 and 5. Not sure what could be the impact or problem about metrics, …

[image] manueljordan: Not sure what could be the impact or problem about metrics , but about dashboards I would think in two of them to be generated, one for main and other for test . Of course the developer should be strictly controlled for the former in case of error, etc. I mean the current a…

[image] reitzmichnicht: No distinction between main and test please Yes, even with that, we should assume that some plugin for JUnit and TestNG should be created for testing. Same point for Spock and Kotlin.

In my case, SonarLint is applying equally to main and test and I would like that to change. My best example is the rule about Magic Numbers, which should almost always be replaced with named constants in production code, but I don’t think that’s true for test code. I think a test case is a lot mor…

Basically for all languages :slight_smile: Our testers use Selenium/Webdriver to automate unit tests (from inside a C# test project), and they should also have their test scripts evaluated. Would be awesome to have!

-Dsonar.sources=src -Dsonar.tests=target/test-classes/com -Dsonar.test.exclusions=target/test-classes/com such parameters allow to check entire code (including tests) as Main sources. where target/test-classes/com - it’s just an any folder which will not be really verified and it’s just specified …

Is there some status available of it? Which rules was enabled? eg rule java:S1128 is still not available for tests classes.

Allow enabling sonar rules for test sources

Suggest new features

reitzmichnicht (Michael Düsterhus) October 23, 2018, 7:38am 5

No distinction between main and test please. Just put the test violations to the normal issues

Topic		Replies	Views
Thousands of unwanted issues in test code after upgrading to SonarQube 10 SonarQube Server / Community Build java , tests , unit-test	3	93	July 9, 2025
Configuring Custom Sonar Rules Separately for src/main and src/test Rules and Languages	3	175	March 6, 2025
Rule java:S1874 "@Deprecated" code should not be used - in test code Discussions java	15	857	July 12, 2024
Exclude rules from unit tests? SonarQube Server / Community Build	3	3551	February 14, 2019
SonarQube is not identifying code smells or bugs from src/test folder SonarQube Server / Community Build java	9	1441	February 12, 2024

Allow enabling sonar rules for test sources

Related topics