-
Notifications
You must be signed in to change notification settings - Fork 266
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
repository module: Add tests #2228
Comments
This should include the uploader as well. The basic end-to-end test for all examples would be:
This would be useful even without any other checks (like checking which metadata versions are used): if the client can download the file and the contents are correct, that's a really good indication the examples are running pretty well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Once #2193 is merged, there is a repository module. The module is not really tested but should be.
It's entirely possible that the module can't really be effectively unit tested (as it's an ABC). But the repository example can be end-to-end tested and maybe even the SimpleRepository class within the example could be unit tested. I think testing the whole repository example is most critical.
I'm not sure what kind of things we should test but at least
The text was updated successfully, but these errors were encountered: