Closed
Conversation
Member
|
At first glance This breaks fixture scope based ordering |
Member
Does pytest does any reordering currently based on session-scoped fixtures? Other than that, I'm not sure this is the way to go because it will completely change the expected order of test execution... not that it is guaranteed when using |
Member
|
i have a proposal for general test ordering, will explain at the sprint |
Member
|
closing for now, this solution alters fixture setup/teardown expectations and one of the goals is to teach xdist about the scopes and caches to better utilize each nodes scoped caches |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes pytest-dev/pytest#596 (and maybe also pytest-dev/pytest#920, but I can't reproduce it).