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: Jack Riches (BitBucket: jriches, GitHub: jriches)
If test is marked xfail, but the test passes, there should be a non-zero exit code (e.g. for CI to flag a warning).
I believe this once existed, as documented by the release notes for 2.0.0:
“xpass” (unexpected pass) tests don’t cause exitcode!=0
The text was updated successfully, but these errors were encountered:
Original comment by Ronny Pfannschmidt (BitBucket: RonnyPfannschmidt, GitHub: RonnyPfannschmidt):
seems i introduced that between 1.3 and 2.0 - i didnt document it extensively enough, so i'll check again in detail how it came up
Sorry, something went wrong.
I also raised this in #716
See #814 for the discussion about flaky tests.
I'm closing this as a duplicate of the ongoing discussion at #814, thanks @dariuspbom for bringing this to attention.
No branches or pull requests
Originally reported by: Jack Riches (BitBucket: jriches, GitHub: jriches)
If test is marked xfail, but the test passes, there should be a non-zero exit code (e.g. for CI to flag a warning).
I believe this once existed, as documented by the release notes for 2.0.0:
The text was updated successfully, but these errors were encountered: