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
Originally created by @pandemicsyn on 2021-09-30 15:18:18
This is a bit of a meta/informational issue - but while helping with https://gitlab.com/meltano/meltano/-/merge_requests/2349 (small bug in controllers/orchestrations) realized we have some bigger gaps in our test coverage. So I ran a "quick" coverage report. Here's the raw result (but feel free to skip ahead, I include two top 20 reports):
This second one is sorting by # of statements missed. I feel like that's sometimes more indicative of where you've got real gaps. Case in point, orchestrations.py is #1 on this list:
We've got some gaps (quite a few in controllers it seems like) but its nothing terrible. We can improve coverage for some of these as we're working on issues in adjacent areas, as long as we're diligent and look out for them.
We could also break out some small explicit issues to sprinkle throughout a few dev cycles (i.e. improve test coverage for fileX style issues). @aaronsteers@tayloramurphy I'm not sure how you'd prefer to tackle tech debt like this, but one thing I've also seen at gigs in the past is having tech debt/clean up focused dev days every so often.
The text was updated successfully, but these errors were encountered:
This has been marked as stale because it is unassigned, and has not had recent activity. It will be closed after 21 days if no further activity occurs. If this should never go stale, please add the evergreen label, or request that it be added.
Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2959
Originally created by @pandemicsyn on 2021-09-30 15:18:18
This is a bit of a meta/informational issue - but while helping with https://gitlab.com/meltano/meltano/-/merge_requests/2349 (small bug in controllers/orchestrations) realized we have some bigger gaps in our test coverage. So I ran a "quick" coverage report. Here's the raw result (but feel free to skip ahead, I include two top 20 reports):
Raw coverage report
Top 20
That above is large list to grok, so here's two top 20's. The first is a top 20 files sorted by coverage percentage:
This second one is sorting by # of statements missed. I feel like that's sometimes more indicative of where you've got real gaps. Case in point, orchestrations.py is #1 on this list:
Thoughts
We've got some gaps (quite a few in
controllers
it seems like) but its nothing terrible. We can improve coverage for some of these as we're working on issues in adjacent areas, as long as we're diligent and look out for them.We could also break out some small explicit issues to sprinkle throughout a few dev cycles (i.e.
improve test coverage for fileX
style issues). @aaronsteers @tayloramurphy I'm not sure how you'd prefer to tackle tech debt like this, but one thing I've also seen at gigs in the past is having tech debt/clean up focused dev days every so often.The text was updated successfully, but these errors were encountered: