Skip to content

fix: correctly set fixture when using markers#42

Merged
miketheman merged 1 commit intomasterfrom
miketheman/fix15-close28
May 31, 2020
Merged

fix: correctly set fixture when using markers#42
miketheman merged 1 commit intomasterfrom
miketheman/fix15-close28

Conversation

@miketheman
Copy link
Copy Markdown
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