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.

Sign up for GitHub

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

Jump to bottom

Analyze code coverage and add badge #73

Closed
Tracked by #81
Gigas002 opened this issue Aug 5, 2020 · 2 comments
Closed
Tracked by #81

Analyze code coverage and add badge #73

Gigas002 opened this issue Aug 5, 2020 · 2 comments
Assignees
@Gigas002
Labels
enhancement New feature or request grabbed Someone's already working on this issue
Projects
Repo organization
Milestone
2.0.0

Comments

@Gigas002
Copy link
Owner

Gigas002 commented Aug 5, 2020

Depends on #28
@Gigas002 Gigas002 added enhancement New feature or request grabbed Someone's already working on this issue labels Aug 5, 2020
@Gigas002 Gigas002 added this to the 2.0.0 milestone Aug 5, 2020
@Gigas002 Gigas002 self-assigned this Aug 5, 2020
@Gigas002 Gigas002 added this to To do in Repo organization via automation Aug 5, 2020
@Gigas002 Gigas002 mentioned this issue Aug 6, 2020
Closed
17 tasks
@Gigas002 Gigas002 added the help wanted Extra attention is needed label Aug 12, 2020
@Gigas002
Copy link
Owner Author

Didn't find out how to measure test coverage by CodeCov through OpenCover or through CI (github action addon, appveyor docs). This stuff isn't working or targets MSTest/XUnit (I use NUnit for my tests).
Would appreciate PR or explanation on how to use it.

@Gigas002 Gigas002 removed the help wanted Extra attention is needed label Aug 13, 2020
@Gigas002
Copy link
Owner Author

That shit doesn't work in CI no matter what I do (tried both coverlet.msbuild and coverlet.collector) and even running it locally was painfull (who knew, that -c Release breaks the results?)
So I've decided to create coverage reports locally and send them to server myself. See codecov-local.ps1 script.

Repo organization automation moved this from To do to Done Aug 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Gigas002 Gigas002

Labels
enhancement New feature or request grabbed Someone's already working on this issue
Projects
Repo organization
  
Done
Milestone
2.0.0
Development

No branches or pull requests
1 participant
@Gigas002