also, for projects that contain only POCOs and serializable objects (that must have a setter), I don’t really care about Condition Coverage, as I don’t want to have to test setters that will ultimately only be called by a serialization framework.

hi @larryautravail I moved your message on a separate topic to be able to discuss here regarding [image] C#/VB.NET: SonarQube and SonarCloud support Branch/Condition Coverage data Is there a way to disable this feature? Our coverage just dropped into oblivion and there is no real way for us to…

We’re released sonar-dotnet 8.6.1 , fixing the branch coverage import bug when importing data from multiple test projects. It will get deployed to :sonarcloud: in the following days. You should expect branch (conditional) code coverage to increase. To be clear: we fixed the import of branch cover…

Dotnet setter code coverage in serialization scenarios

SonarQube Cloud

Andrei_Epure (Andrei Epure) April 9, 2020, 2:04pm 2

hi @larryautravail

I moved your message on a separate topic to be able to discuss here

regarding

can you please share with us more details? how much did your code coverage drop? is it just because POCO serializable objects with uncovered setters or is there something else?

Topic		Replies	Views
Pull requests failing to uncovered conditions SonarQube Cloud coverage , dotnet	11	6975	May 18, 2020
C#/VB.NET: SonarQube and SonarCloud support Branch/Condition Coverage data Sonar Updates csharp , vbnet , coverage , dotnet	10	7397	April 27, 2021
Conditions Coverage Is Missing SonarQube Server / Community Build msbuild , coverage , bug-no-category	2	1760	April 26, 2021
C# branch code coverage in SonarCloud problem with iterator SonarQube Cloud coverage , dotnet , sonarqube-cloud	6	3116	April 29, 2020
Feature Request: Import Visual Studio coverage in Cobertura format Suggest new features csharp , sonarqube , coverage , dotnet , bump	2	392	September 20, 2023

Dotnet setter code coverage in serialization scenarios

Related topics