Replies: 2 comments 4 replies
-
|
For taking snapshots we have code coverage metrics generated -- and of course these have been used to improve coverage. However there's also an issue about tracking coverage over time. We'd need to instrument our ci, catch the data, and report. Not necessarily hard, but takes a little time. Using a tool that makes this easy, and can visualize for reporting could be useful - though I think a £$ is involved? Generally i'd prefer to do what we can with open source tooling, and not make things too complex.... but not hard adding if it's not a hard requirement but added value that saves us time & improves quality |
Beta Was this translation helpful? Give feedback.
-
|
Given that we only had 1 response, I'm going to take that as this is not something we should spend our time on now when there are lots of other things we could be doing. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
In a number of projects I've worked on before, we've used CodeCov for checking code coverage.
Opening a poll here to gauge interest in using CodeCov with Mellea.
1 vote ·
Beta Was this translation helpful? Give feedback.
All reactions