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
pytest.ini
On the wave of deprecation rules, here's another idea. The linter could check if the config is following the best practices:
xfail_strict = True
junit_family = xunit2
addopts
filterwarnings
error
-ra
--durations
minversion
testpaths
pyargs
norecursedirs
The default pytest config is not strict enough.
The text was updated successfully, but these errors were encountered:
NB: since pytest 6.0.0, the options can also reside in pyproject.toml. Docs
Sorry, something went wrong.
strict=
@pytest.mark.xfail
No branches or pull requests
Rule request
Description
On the wave of deprecation rules, here's another idea. The linter could check if the config is following the best practices:
xfail_strict = True
(per https://pganssle-talks.github.io/xfail-lightning/)junit_family = xunit2
(makes pytest's warnings go away)addopts
args on separate lines (makes it easier to annotate the purpose with comments, ref https://github.com/ansible/pylibssh/blob/a2453ed/pytest.ini#L2-L16)filterwarnings
should haveerror
on the first line (rest of the lines could be legit temporary ignores)-ra
inaddopts
--durations
inaddopts
minversion
should be settestpaths
orpyargs
should be specifiednorecursedirs
presentRationale
The default pytest config is not strict enough.
The text was updated successfully, but these errors were encountered: