-
Notifications
You must be signed in to change notification settings - Fork 79
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
#1014 storage fixtures #1054
#1014 storage fixtures #1054
Conversation
eca0d3b
to
8c0632c
Compare
a8a4750
to
bc52811
Compare
38c856e
to
314f20c
Compare
Would be nice to add some evidence (sorted output of pytest discovery before and after and a diff, maybe?) to demonstrate that the test cases we execute are similar before and after this change. |
@poodlewars There's no change in this PR on what storage the tests will run against; that's in the next PR. This PR is mainly moving the same fixtures to a new API framework and using the API in tests. |
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.
--WIP review: I haven't read the diff in the tests/
tree yet.--
Done now.
I've found at least a few tests deleted in this PR, so I do think that some comparison would be helpful. |
Thanks for this, overall this looks like a big big cleanup to some tech debt that has been accruing for a long time. It's really nice seeing the cleaned up form taking shape. To summarize my main concerns,
My other comments are much more minor and localized. |
Please refer to the files at https://arcticdb.slack.com/archives/C0553TEJ63F/p1700586140886959 Both files are obtained using
The only meaningful difference is |
0581e3f
to
d314348
Compare
This reverts commit 1b92535.
This reverts commit 5505fa4.
... without formatting to avoid conflicts
* Standard, not pytest-coupled API for storage fixture life cycles * Methods for setting permissions and shutting down the fixtures independent of pytest for error handling testing * Proper cleanup and exception handling to allow tests to run concurrently and independently of earlier failures * PrefixingLibraryAdapterDecorator to support isolating Mongo fixture instances, but can be used with any other Storage type
+ simplified some of them + remove pytest-split
d314348
to
03dd083
Compare
Reference Issues/PRs
#1014
What does this implement or fix?
Introducing the StorageFixtures framework