-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Fix pytest.mark.skip mark when used in strict mode #1472
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
Conversation
Thanks! Is there an issue for the bug open already? Feel free to add yourself to authors regardless, a testcase is already half the fix 😉 (or don't, if you prefer not to). |
@The-Compiler thanks for the reactivity! I didn't find an issue, no. Should I open one? |
Line 33 in cbb5d48
happy hacking |
Ah, I was searching where they were defined, but @RonnyPfannschmidt was faster 😆 |
Oops, I just noticed that @pquentin while you're at it, would you mind adding that parameter to |
@nicoddemus Sure, but I'll do it in a different PR to avoid confusion because it's a different strict parameter. |
I think the changes are related (updating the list of markers), but do as you prefer, sure! Thanks! 😁 |
@nicoddemus It's in the PR, but in a different commit. You guys are amazing, thanks for commenting on this PR this quickly. I think it's ready for review (if CI passes). |
@@ -5,9 +5,12 @@ | |||
|
|||
* | |||
|
|||
* | |||
* Add `strict` parameter to xfail marker. Thanks `@pquentin`_ for the | |||
PR and `@nicoddemus`_ for noticing the issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is confusing, as it's only a doc fix, right? IMHO, I don't think this should be mentioned in the changelog at all.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@The-Compiler Thanks. I removed the entry from the changelog and mentioned "doc" in the commit.
The travis issue appears to be coverall's fault? https://travis-ci.org/pytest-dev/pytest/jobs/117691035 |
Seems like: lemurheavy/coveralls-public#741 |
the rest looks good, i wonder if we should allow failures from coveralls |
Fix pytest.mark.skip mark when used in strict mode
thanks for the work - well done :) |
The comprehensive test suite, the well-written code and the help from all three of you made this easy Thanks! |
The `--strict` argument was removed in pytest-dev#2552, but the removal wasn't actually correct - see pytest-dev#1472.
This targets master since it's a bug, but no CHANGELOG or AUTHORS since I'm only sending a xfail test. Should I still do something to one of those files?