-
-
Notifications
You must be signed in to change notification settings - Fork 308
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
[TST] Bring test coverage to 100% #2614
Comments
Test coverage is now being tracked on Codecov -- https://app.codecov.io/gh/zarr-developers/zarr-python/tree/main Marking this as "Help Wanted" to start soliciting contributions to fill in test gaps. |
I'm working a bit on the storage related testing. I expect these can all be addressed in a single coherent PR, but please let me know if you'd rather smaller PRs bringing addressing each module separately.
|
that's great to hear @maxrjones -- I was also working on expanding store tests in #2447, but that PR is super outdated by now. nonetheless it might be helpful to see some of the changes I made to test fixtures, namely pulling the fsspec stuff into the main set of store fixtures |
Oh nice, I didn't see that so thanks for sharing! would you rather update/continue that PR rather than review a different one? I don't want to spend time where it's not necessary. |
it's been a while since I worked on that PR, and I don't have time to keep working on it at the moment, so it's very likely that bringing it up to date will be a lot of work. If you think the merge conflicts aren't too bad, then it might save you some time to build on it, but otherwise I would just use it as an example of a similar effort, and you should feel free to copy + paste stuff from it as needed. |
As of today, Zarr-Python's main branch has a test coverage of 87%. We should strive to bring this back to 100%. Here is the current report:
The text was updated successfully, but these errors were encountered: