Skip to content

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

Merged
merged 2 commits into from
Mar 22, 2016

Conversation

pquentin
Copy link
Contributor

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?

@The-Compiler
Copy link
Member

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).

@pquentin
Copy link
Contributor Author

@The-Compiler thanks for the reactivity! I didn't find an issue, no. Should I open one?

@RonnyPfannschmidt RonnyPfannschmidt added type: bug problem that needs to be addressed status: help wanted developers would like help from experts on this topic good first issue easy issue that is friendly to new contributor labels Mar 22, 2016
@RonnyPfannschmidt
Copy link
Member

config.addinivalue_line("markers",
needs another line to fix it - feel free to add it and put yourself in the changelog/authors file

happy hacking

@The-Compiler
Copy link
Member

Ah, I was searching where they were defined, but @RonnyPfannschmidt was faster 😆

@nicoddemus
Copy link
Member

Oops, I just noticed that xfail description in the same place is lacking docs for the new strict parameter.

@pquentin while you're at it, would you mind adding that parameter to xfail's docs as well? 😁

@pquentin
Copy link
Contributor Author

@nicoddemus Sure, but I'll do it in a different PR to avoid confusion because it's a different strict parameter.

@pquentin pquentin changed the title xfail: strict mode reports skip mark unregistered Fix pytest.mark.skip mark when used in strict mode Mar 22, 2016
@nicoddemus
Copy link
Member

I think the changes are related (updating the list of markers), but do as you prefer, sure!

Thanks! 😁

@pquentin
Copy link
Contributor Author

@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.
Copy link
Member

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.

Copy link
Contributor Author

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.

@pquentin
Copy link
Contributor Author

The travis issue appears to be coverall's fault? https://travis-ci.org/pytest-dev/pytest/jobs/117691035

@The-Compiler
Copy link
Member

Seems like: lemurheavy/coveralls-public#741

@RonnyPfannschmidt
Copy link
Member

the rest looks good, i wonder if we should allow failures from coveralls

RonnyPfannschmidt added a commit that referenced this pull request Mar 22, 2016
Fix pytest.mark.skip mark when used in strict mode
@RonnyPfannschmidt RonnyPfannschmidt merged commit 6ddfd60 into pytest-dev:master Mar 22, 2016
@RonnyPfannschmidt
Copy link
Member

thanks for the work - well done :)

@pquentin
Copy link
Contributor Author

The comprehensive test suite, the well-written code and the help from all three of you made this easy Thanks!

@coveralls
Copy link

Coverage Status

Coverage increased (+0.0009%) to 92.257% when pulling 4559c11 on pquentin:master into 890c2fa on pytest-dev:master.

The-Compiler added a commit to The-Compiler/pytest that referenced this pull request Mar 3, 2021
The `--strict` argument was removed in pytest-dev#2552, but the removal wasn't
actually correct - see pytest-dev#1472.
The-Compiler added a commit that referenced this pull request Mar 4, 2021
* Fix test_strict_and_skip

The `--strict` argument was removed in #2552, but the removal wasn't
actually correct - see #1472.

* Fix argument handling in pytest.mark.skip

See #8384

* Raise from None

* Fix test name
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue easy issue that is friendly to new contributor status: help wanted developers would like help from experts on this topic type: bug problem that needs to be addressed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants