Moved pytest.xfail to pytest.mark.xfail #1376
Merged
Conversation
This file contains 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
kclowes
force-pushed
the
pytest-mark-xfail
branch
2 times, most recently
from
fac146f to
e5373e8
Compare
kclowes
force-pushed
the
pytest-mark-xfail
branch
from
e5373e8 to
c1a5536
Compare
kclowes
changed the title
pipermerriam
approved these changes
Jul 8, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What was wrong?
pytest.xfailmakes the test unconditionally xfail, and no code after thexfailis run. The@pytest.mark.xfaildecorator lets the test run.Related to Issue #1341
How was it fixed?
Added @pytest.mark.xfail where appropriate, and removed xfails on tests that are passing
Cute Animal Picture