-
Notifications
You must be signed in to change notification settings - Fork 121
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
Build out the custom extension tests #974
Conversation
6ae6d0b
to
18223d0
Compare
Codecov ReportBase: 90.09% // Head: 90.09% // No change to project coverage 👍
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more Additional details and impacted files@@ Coverage Diff @@
## main #974 +/- ##
=======================================
Coverage 90.09% 90.09%
=======================================
Files 47 47
Lines 6090 6090
Branches 915 915
=======================================
Hits 5487 5487
Misses 422 422
Partials 181 181 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 at Codecov. |
99% coverage! Probably should bump up the |
801e096
to
c584201
Compare
99% only for the tests :-) ... base coverage is still 91%. Also ironic that increasing the test coverage doesn't increase project coverage, which makes me wonder what we're even doing here. Ah well, hopefully this will all get reworked as a part of #448 anyways. |
Ah. Oops. Yeah. |
Related Issue(s):
Description:
After further inspection, the only real test file that wasn't really being exercised was
extensions/test_custom.py
. This PR builds out some extension tests, and removes some sections that were mostly just testing tests (aka not useful tests for the main codebase).IMO this is Good Enough™ coverage in the test suite, most of the missed lines are conditionals in mocks:
PR Checklist:
pre-commit run --all-files
)scripts/test
)