-
Notifications
You must be signed in to change notification settings - Fork 186
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
ci: integrate with Codecov for test coverage #211
Conversation
Codecov Report
@@ Coverage Diff @@
## master #211 +/- ##
=========================================
Coverage ? 62.34%
=========================================
Files ? 49
Lines ? 4002
Branches ? 0
=========================================
Hits ? 2495
Misses ? 1352
Partials ? 155 |
layout: "header, diff" | ||
behavior: default | ||
require_changes: no | ||
|
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.
This is largely a default config, with the only changes so far being:
- removal of notifications for the time being
- lowered the 'range' (preferred range, among other settings to be decided)
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.
👍
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.
Also added a list of files that are impacted by the pull request and their coverage to the PR comment that is left.
What do we need to merge this @Jusshersmith ? |
@jphines I think it's fine to merge as is - we'll work out the exact configuration we prefer as time goes on, but everything seems to be working well enough to start with! Also once this is merged I think the reports become more useful as they'll have master to compare against. |
Problem
We already try hard to make sure code has appropriate tests written, however we don't currently provide an easy way to monitor and track test coverage.
Solution
Integrate the sso repo with a tool like Codecov, which helps us track and monitor coverage reports and make them a prominent part of pull requests and the contribution workflow.
Notes
This currently uses the Codecov bash uploader to upload coverage reports, which is one of the recommended methods. Other methods include updating CircleCI to version 2.1 and making use of CircleCI orbs.
Specific settings for codecov to be decided - this PR has been created with defaults.