-
Notifications
You must be signed in to change notification settings - Fork 1
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
Improve Testing Infrastructure #87
Conversation
19a8959
to
e9986a4
Compare
f040029
to
d7a31ae
Compare
d7a31ae
to
a22252a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was originally hesitant about removing so much API code, but after some thought I agree that shrinking our API surface to only what we actively use is a good approach for now, especially in the context of fully testing the API. We only need to worrry about a robust API when we get users that would leverage it.
I'm excited about this new test suite, especially since it helped reveal some bugs that you fixed. The permissions testing is much stronger now, and I'm glad for the time we'll get back by scheduling the slow tests.
Just a few questions on minor things, but overall this looks good.
This PR improves the testing infrastructure of the UVDAT API, through the addition of pytest fixtures, factory-boy factories, and some core tests. These tests aren't fully expansive, and don't cover every possible scenario, but instead attempt to test the core business logic that is already implemented. Many of the default views that we leverage from DRF are not explicitly tested, as we do very little (if any) modification of those viewset behaviors, and as such we would simply be testing DRF itself.
Some side effects of this PR: