Closed arunkannawadi closed 1 year ago
I've learned some things here about coverage configuration that I'm looking forward to applying in middleware packages, too.
I'm very glad about that! I pushed a pre-commit
hook that will check the validity of the config file, if changed. This could be helpful if you'd like to play with the configs elsewhere as well.
I almost commented that your logic to build a simple MultipleCellCoadd data structure for testing should get moved to test_utils.py
It could still go there and get called once in setUpClass
. I was also considering that at some point.
The pre-commit hook I added that checks the validity of the codecov config works fine on my local dev environment (at USDF). I've checked it explicitly by making the config file invalid and ensuring that the pre-commit hook notifies me of that. But pre-commit.ci fails to reach the server on Github Actions. This is not a required check at the moment, and I am going to ignore this for now, since the pre-commit hook is intended to be on the developer side of things, not necessarily as a CI/CD functionality.
Codecov Report
54.05% <54.05%> (ø)
94.00% <94.00%> (ø)
100.00% <100.00%> (+9.43%)
98.42% <100.00%> (+0.01%)
97.43% <100.00%> (+0.37%)
47.61% <0.00%> (-3.05%)
42.00% <0.00%> (-0.72%)
65.15% <0.00%> (-0.33%)
81.57% <0.00%> (+1.09%)
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.