-
Notifications
You must be signed in to change notification settings - Fork 482
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
Refactor integration test fixtures #456
Conversation
ca52bb5
to
849c93f
Compare
ea8cf76
to
f1cebe3
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.
Great Work! some nitpicks I have added
f1cebe3
to
50f1de7
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.
Great, let's get this merged.
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.
So I didn't lose interest in the second half :-P, I just didn't see anything to suggest.
50f1de7
to
098c5d6
Compare
Description
This PR refactors the test fixtures. It creates separate
conftest.py
files for the integration and unittests,and then simplifies the fixtures in the
conftest.py
file for the integration tests. This was necessary asthere were so many layered fixtures that it was hard to tell what the initial state was before any test ran.
The refactor of the test fixtures also led to some changes in the original tests. I do not believe that I have
altered them in any substantial way, but they should be checked just in case.
I have also refactored the
server
API slightly, to make it more amenable to testing. I don't believe that this has any major impact on the code.A later PR will do something similar for the unittests.
Related Issue(s)
#388
Checklist
sphinx
format docstrings added or updated.Additional Notes
The project really needs to figure out what it means by integration and unittests! A bunch of the current 'unittests' take longer than the integration tests, and have at least as much coupling to a live database service.