Is it possible to get coverage by tests?

[yamac-kurtulus]

I looked for, but couldn't find an answer. Is it possible to find information about which tests cover what part of the code? If not, do you plan to implement it?

[tonerdo]

HI @yamac-kurtulus, the different output file formats contain that information. You can use https://github.com/danielpalme/ReportGenerator with the Opencover and Cobertura output formats

[default-writer]

you can see it in Visual Studio 2017

[yamac-kurtulus]

@tonerdo,
I am using the report generator both with cobertura and opencover formats using coverlet. However it did not show it. Yes, the code-coverage from coverlet is there, however there is no information on which tests covering what parts of the code. Do I need a switch or parameter while testing? I am excluding tests from the coverage report, could this be causing a problem? Likewise, is it possible that it won't find xunit tests?

Note: Thanks for the awesome code coverage tool by the way. Coverlet is great and I want to keep using, but I need the coverage by tests info :/

@hack2root thank you for the advice, however I think it is possible in VS professional, I am using community edition. Besides, I want to publish output results using report generator and not stick to VS.

[latop2604]

FYI, It's an enterprise feature, not professional

[yamac-kurtulus]

@latop2604 that's even harder for me to get then, oh well :/

[lucasteles]

Hi, any update about this? this feature is very usefull and we cant use it today

[MarcoRossignoli]

I'm not sure that is possible with current file format FWIK coverage format fail save only branches/sequence points visited but we don't know who is the test top caller.
I think that this feature should integrate with tests platform(i.e. xunit).
I don't know how vs do it, maybe @vagisha-nidhi can help here or can direct us to correct team, or also @bradwilson(xunit) could tell us if know something about it.

[github-actions]

This issue is stale because it has been open for 90 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 275 days since being marked as stale.