-
-
Notifications
You must be signed in to change notification settings - Fork 353
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
test: use xfail_strict
for pytest config
#2328
Conversation
I am not safe merging this without proper Windows CI, since a lot of xfails are Windows-related. Can I / someone else trigger it manually somehow? |
What about temporarily making a commit that removes |
Done:
I will now revert Later we can add more correct way to handle flaky tests, I propose to add https://github.com/box/flaky or https://pypi.org/project/pytest-repeat/ to do the job properly. |
Kudos, SonarCloud Quality Gate passed!
|
Documentation preview will be available shortly at https://litestar-org.github.io/litestar-docs-preview/2328 |
One more check that I forgot in #2327
Looks like we have several
xfail
tests:Without
xfail_strict
test can pass and pytest won't report unexpected pass as an xfail error. With this setting it will.Docs: https://docs.pytest.org/en/7.1.x/how-to/skipping.html#strict-parameter