We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Originally reported by: Ronny Pfannschmidt (BitBucket: RonnyPfannschmidt, GitHub: RonnyPfannschmidt)
as reported by fijal
i also think xfails shouldnt trigger the debugger unless requested
The text was updated successfully, but these errors were encountered:
Original comment by Jurko Gospodnetić (BitBucket: jurko, GitHub: jurko):
Just tested this with:
import pytest @pytest.mark.xfail(reason="bad test") def test_example(): assert False
and running it I get the following output:
D:\Example>py3 -m pytest --pdb ============================= test session starts ============================= platform win32 -- Python 3.3.3 -- pytest-2.5.2.dev1 collected 1 items test_xxx.py x ========================== 1 xfailed in 0.03 seconds ==========================
So I think this issue has already been resolved.
This has been tested on Windows 7 x64 SP1 with full updates. Python and pytest versions may be seen in the output quoted above.
Hope this helps.
Best regards, Jurko Gospodnetić
Sorry, something went wrong.
Original comment by holger krekel (BitBucket: hpk42, GitHub: hpk42):
Thanks, Jurko. I vaguely remember this has been fixed some time ago, indeed.
No branches or pull requests
Originally reported by: Ronny Pfannschmidt (BitBucket: RonnyPfannschmidt, GitHub: RonnyPfannschmidt)
as reported by fijal
i also think xfails shouldnt trigger the debugger unless requested
The text was updated successfully, but these errors were encountered: