Consider making a class library for reading the coverage reports generated with coverlet.collector

[AraHaan]

Currently I have a project where I test my project on and with my local WSL Linux install the coverage does not say 100% but on Windows it does, for this reason I want to use code to read the coverage report into a Windows Forms application and do the following:

• Background Color the lines FULLY covered in Green
• Background Color the lines PARTIALLY covered in Yellow
• Background Color the lines NOT covered at all in Gray

Currently I could hard code it to read the xml report, except the coverage reports could be outputted in json or some other format so having an official coverlet classlib that can help implement coverage report reading would be a must for me.

Why do I want this? Visual Studio's Analyze Code Coverage for All Tests options in the menu does not have the option to "use WSL to obtain the coverage results". Just to see what lines are not covered specifically on Linux which are covered on Windows. Having this information is a must for me to have and the best way is for me to make a tool that reads the coverage reports and shows them which exact file and lines are causing the difference in coverage on a specific OS that is used to run the tests (which might be useful in finding and quickly fixing possible bugs on those systems).

[AraHaan]

@Bertk mind letting me know if this is possible for coverlet to implement so that way all I can do is write the winforms program that uses the classlib and it properly doing its thing to do the highlighting mentioned above (I feel like me making the winforms project would be a great tool to have for others to use).

[Bertk]

Thank you for this question.

Could you please explain why you are not using dotnet-reportgenerator-globaltool

We use this tool for the coverlet CI and it shows which lines and branch is covered | partially covert | not covered.

e.g. report for active PR Ensure type/method refs use target module's core library class.

[AraHaan]

Could you please explain why you are not using dotnet-reportgenerator-globaltool

I was thinking of making my own similar global tool using winforms that simply allows me to see the actual parts of the code that is covered/partially covered/not covered directly (without writing another file that would then need to be opened). Not going to lie the tool might help, but it would also help having a tool that is similar to the Analyze Code coverage for All Tests that Visual Studio has but it has a fatal flaw in that feature of Visual Studio which is to figure out why the coverage can randomly get lower than what it is on Windows as soon as the tests run within WSL Ubuntu 24.04 (which is a pain for checking if there is a bug in the Linux side of the code) 😂.