Sonarcloud old unit test code smell reappearing in new code analysis

[Colin]

Hey there.

@Chandrima

It should be categorized as test project because the project name has ‘UnitTests’ in it.

The previously linked post indicates that this is no longer the criteria used to determine if a project is a test project.

@Alexandre_Gigleux

Indeed, we guess that a project of your Solution contains only test files by looking at its name. If the name contains “Test” or “Tests”, then it is automatically considered as a test project and the analyzer will run only the test rules in SonarLint (they are not analyzed at all on SonarQube or SonarCloud for now).

While this was convenient to avoid raising issues that will never be fixed on your test files, this is having a negative impact especially for new users discovering our products. Generally these new users create a simple fake solution made of bad code to evaluate our offering.

Because these users are just testing, they generally name their project “SonarTest”, “TestSonar” and as explained before, SonarCloud/SonarQube will raise nothing on them which would give the feeling that our products don’t detect any issue in the code.

Upcoming Change

We believe there is a better way to do this and we’re submitting it to you. In the coming weeks, a project will be considered as a “test” project only if it has some dependencies on test artifacts independently of its name.

It will be still possible to explicitly mark a project as being a test or main project by setting the MSBuild property <SonarQubeTestProject> to true or false e.g.

<PropertyGroup>
   <SonarQubeTestProject>true</SonarQubeTestProject>
</PropertyGroup>

The related documentation will be updated accordingly as soon as the change is effective.

Therefore, it’s worth checking how the project being categorized (looking at the analysis logs)

Please note this is a Community forum with volunteers offering help in using SonarSource produccts – this is not an issue tracking system.