-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add coverage build and upload unit-test coverage to codecov.io #268
Conversation
* Solves #120. * Adds a coverage build to CMakeLists. Currently this is only for the `tdms_tests` executable. Could also add it to `tdms` itself if we wanted to check the system tests' coverage. * In the CI GH action, I install lcov (for nice summaries of the coverage stats for humans, and for upload to codecov.io). * Add a badge 🎉 (bit we need to add a token).
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #268 +/- ##
=======================================
Coverage ? 47.56%
=======================================
Files ? 63
Lines ? 7804
Branches ? 0
=======================================
Hits ? 3712
Misses ? 4092
Partials ? 0 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only thing to flag is that we should probably make our stance on Windows-testing a bit clearer, but that's not a bug introduced with these changes.
@@ -43,7 +43,8 @@ jobs: | |||
# also test 'Release'. | |||
build_testing: [ON, OFF] | |||
exclude: | |||
# Currently our tests don't compile in Windows so skip this. | |||
# Currently our tests don't compile, and nor do we have a coverage | |||
# build in Windows so skip this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😬 Should this maybe be an issue or are we committing to not supporting Windows?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm inclined to say no. I softly doubt any of Peter's future developers will be using Windows.
Could tack this on to...
...?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a completely different tool to gcov
, though. Also, I don't know how to run it... maybe Mosè does?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, what is "It" here? lcov
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess I mean this Microsoft.CodeCoverage.Console tool.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Windows? What's Windows?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🍉
Context/Description
Adds a coverage build to CMakeLists and additions to the GitHub action to upload it all to codecov.io.
More details
tdms_tests
executable. Could also add it totdms
itself if we wanted to check the system tests' coverage.lcov
(for nice summaries of the coverage stats for humans, and for upload to codecov.io).Testing
Tested over on my fork.
Documentation