-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show code coverage in report #2662
Comments
That would be indeed beneficial.
In short, this is an interesting objective, but I do not see this happening in a near or medium future |
that being said, the mutation coverage data can be published. But, again, this is a different report. |
We might be able to reuse the coverlet collector https://github.com/coverlet-coverage/coverlet/blob/master/src/coverlet.collector/DataCollection/CoverletCoverageCollector.cs |
We could capture code coverage as part of the initial test run (that could be used as a normal test run BTW), but no use benefit beyond that. I am probably missing something important, but:
There are also significant hurdle to address
|
@dupdob I don't think we need to use the coverage information to determine mutant coverage. We can keep that like it is. We just need to add coverage analysis to the initial testrun and get the percentage from it. The initial testrun doesn't contain mutations so the coverage should be correct. |
oh, ok. I feel better then :-) |
If possible I would like if it showed the normal overall code coverage in the final stryker report, so I don't have to separately run a code coverage test.
The text was updated successfully, but these errors were encountered: