Skip to content

Conversation

@refi64
Copy link

@refi64 refi64 commented Jun 18, 2016

Fixes pytest-dev/pytest#596 (and maybe also pytest-dev/pytest#920, but I can't reproduce it).

@RonnyPfannschmidt
Copy link
Member

At first glance This breaks fixture scope based ordering

@nicoddemus
Copy link
Member

At first glance This breaks fixture scope based ordering

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 pytest-xdist anyway. Any other thoughts?

@RonnyPfannschmidt
Copy link
Member

i have a proposal for general test ordering, will explain at the sprint

@RonnyPfannschmidt
Copy link
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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants