Skip to content
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

fix: correctly set fixture when using markers #42

Merged
merged 1 commit into from
May 31, 2020

Conversation

miketheman
Copy link
Owner

As reported in a couple of issues, the usage of markers (not fixtures)
was misbehaving, as the order in which the _socket_marker evaluation
was occurring left the command-line option disabled.

Fixes #15
Closes #28

Co-authored-by: Calvin Behling calvin.behling@gmail.com
Signed-off-by: Albert Tugushev albert@tugushev.ru
Signed-off-by: Matt Callaghan mcallaghan-bsm@users.noreply.github.com
Signed-off-by: Mike Fiedler miketheman@gmail.com

As reported in a couple of issues, the usage of markers (not fixtures)
was misbehaving, as the order in which the `_socket_marker` evaluation
was occurring left the command-line option disabled.

Fixes #15
Closes #28

Co-authored-by: Calvin Behling <calvin.behling@gmail.com>
Signed-off-by: Albert Tugushev <albert@tugushev.ru>
Signed-off-by: Matt Callaghan <mcallaghan-bsm@users.noreply.github.com>
Signed-off-by: Mike Fiedler <miketheman@gmail.com>
@miketheman miketheman added the bug Something isn't working label May 31, 2020
@miketheman miketheman merged commit 81b7490 into master May 31, 2020
@miketheman miketheman deleted the miketheman/fix15-close28 branch May 31, 2020 14:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

@pytest.mark.enable_socket doesn't work
1 participant