Skip to content
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

Report test coverage #1854

Open
cdmihai opened this issue Mar 12, 2017 · 3 comments
Open

Report test coverage #1854

cdmihai opened this issue Mar 12, 2017 · 3 comments
Labels
Area: Our Own Build Problems affecting the build or build infrastructure of the MSBuild repo itself. testing triaged
Milestone

Comments

@cdmihai
Copy link
Contributor

cdmihai commented Mar 12, 2017

It would be nice if our CI builds reported test coverage. Ideally, the tooling should be IDE independent.

@cdmihai cdmihai added Area: Our Own Build Problems affecting the build or build infrastructure of the MSBuild repo itself. testing labels Mar 12, 2017
@rainersigwald rainersigwald added this to the Backlog milestone Jan 21, 2022
@stan-sz
Copy link
Contributor

stan-sz commented Jan 16, 2023

Thanks to microsoft/vstest#2874 getting CC numbers is as easy as:

  • referencing latest Microsoft.Net.Test.Sdk
  • use .Net 6.0+
  • dotnet test --collect "Code Coverage;Format=Cobertura"

When using https://github.com/codecov/codecov-action simply pass files: '*.coverage.xml' to get the CC published.

@rainersigwald
Copy link
Member

Since this repo uses test infrastructure from https://github.com/dotnet/arcade/, we can't do that directly. I don't know the current state of Arcade + coverage info.

@stan-sz
Copy link
Contributor

stan-sz commented Jan 18, 2023

See related dotnet/arcade#1946

@AR-May AR-May added the triaged label Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Our Own Build Problems affecting the build or build infrastructure of the MSBuild repo itself. testing triaged
Projects
None yet
Development

No branches or pull requests

4 participants