-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Documentation: confusion between --junit-xml
and --junitxml
#11091
Comments
Thanks for bringing this up, this was a oversight when unifying the argument names while leaving the old ones around |
Hello , I would like to give a try on this please? @RonnyPfannschmidt |
did some more digging and apparently pytest/src/_pytest/config/argparsing.py Lines 489 to 494 in 0ded329
e.g. default argparse behavior shows both aliases
with
|
Looks like that's coming from some 10 years ago here: 007a77c. I'm not sure if it's worth the breakage to deprecate/remove the |
The docs and cli help are a bit confusing around the
--junitxml
/--junit-xml
cli option (and probably some comparable options).pytest --help
only mentions--junit-xml=path
(e.g. also see https://docs.pytest.org/en/7.1.x/reference/reference.html#command-line-flags):However, most examples in the docs (and mosts tests) use
--junitxml
, e.g. https://github.com/pytest-dev/pytest/blob/0ded3297a9749aabad7d3c2447dce98321741dda/doc/en/how-to/output.rst#creating-junitxml-format-files :This was quite confusing to me as it seemed there was a typo somewhere and I lost time just to figure out that they are aliases actually:
pytest/src/_pytest/junitxml.py
Lines 384 to 386 in 0ded329
Wouldn't it be better to stick to one of the two everywhere or at least more explicitly mention that they are aliases?
The text was updated successfully, but these errors were encountered: