You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We started using Codecov to collect coverage statistics back in the heady days of #313. Those were simpler times, when we had an api project and an app project. Our previous coverage statistics provider, Coveralls, didn't support multiple languages at the time, hence the switch.
To say our Codecov coverage collection hasn't scaled gracefully would be putting it mildly. I think we have all collectively experienced the following:
Nonsensical coverage comments on most PRs, including coverage changes for untouched files
In theory, coverage comments on PRs sound really nice. If I add some new code, it's great to have a way of seeing if I forgot to cover some obscure execution path in that code with a test.
In practice, it's hard to trust Codecov's nonsensical coverage comments. 🙁
Would things be better or worse if we applied Codecov to individual projects, instead of the whole repo? Is that even possible? I wonder if our fancy CI that avoids unnecessarily rebuilding unrelated subprojects is messing with our coverage uploads to Codecov, or something.
Overview
We started using Codecov to collect coverage statistics back in the heady days of #313. Those were simpler times, when we had an
api
project and anapp
project. Our previous coverage statistics provider, Coveralls, didn't support multiple languages at the time, hence the switch.To say our Codecov coverage collection hasn't scaled gracefully would be putting it mildly. I think we have all collectively experienced the following:
Could we fix it? Maybe. Does anyone feel like it? I don't. Should we get rid of Codecov? Might be nice.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: