floraachy
/
pytest2
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Improve docs about junit_family warning message 

From discussion in #6178
This commit is contained in:
Bruno Oliveira 2020-05-02 09:55:34 -03:00
parent 5afa8717db
commit 095a195d71
2 changed files with 28 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
doc/en/deprecations.rst
View File

@ -80,22 +80,40 @@ Note that ``from_parent`` should only be called with keyword arguments for the p
.. deprecated:: 5.2 .. deprecated:: 5.2
The default value of ``junit_family`` option will change to ``xunit2`` in pytest 6.0, given The default value of ``junit_family`` option will change to ``xunit2`` in pytest 6.0, which
that this is the version supported by default in modern tools that manipulate this type of file. is an update of the old ``xunit1`` format and is supported by default in modern tools
that manipulate this type of file (for example, Jenkins, Azure Pipelines, etc.).
In order to smooth the transition, pytest will issue a warning in case the ``--junitxml`` option Users are recommended to try the new ``xunit2`` format and see if their tooling that consumes the JUnit
is given in the command line but ``junit_family`` is not explicitly configured in ``pytest.ini``:: XML file supports it.
PytestDeprecationWarning: The 'junit_family' default value will change to 'xunit2' in pytest 6.0. To use the new format, update your ``pytest.ini``:
Add 'junit_family=legacy' to your pytest.ini file to silence this warning and make your suite compatible.
In order to silence this warning, users just need to configure the ``junit_family`` option explicitly: .. code-block:: ini
[pytest]
junit_family=xunit2
If you discover that your tooling does not support the new format, and want to keep using the
legacy version, set the option to ``legacy`` instead:
.. code-block:: ini .. code-block:: ini
[pytest] [pytest]
junit_family=legacy junit_family=legacy
By using ``legacy`` you will keep using the legacy/xunit1 format when upgrading to
pytest 6.0, where the default format will be ``xunit2``.
In order to let users know about the transition, pytest will issue a warning in case
the ``--junitxml`` option is given in the command line but ``junit_family`` is not explicitly
configured in ``pytest.ini``.
Services known to support the ``xunit2`` format:
* `Jenkins <https://www.jenkins.io/>`__ with the `JUnit <https://plugins.jenkins.io/junit>`__ plugin.
* `Azure Pipelines <https://azure.microsoft.com/en-us/services/devops/pipelines>`__.
``funcargnames`` alias for ``fixturenames`` ``funcargnames`` alias for ``fixturenames``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

6
src/_pytest/deprecated.py
View File

@ -49,9 +49,9 @@ NODE_USE_FROM_PARENT = UnformattedWarning(
) )
JUNIT_XML_DEFAULT_FAMILY = PytestDeprecationWarning( JUNIT_XML_DEFAULT_FAMILY = PytestDeprecationWarning(
"The 'junit_family' default value will change to 'xunit2' in pytest 6.0.\n" "The 'junit_family' default value will change to 'xunit2' in pytest 6.0. See:\n"
"Add 'junit_family=xunit1' to your pytest.ini file to keep the current format " " https://docs.pytest.org/en/latest/deprecations.html#junit-family-default-value-change-to-xunit2\n"
"in future versions of pytest and silence this warning." "for more information."
) )
NO_PRINT_LOGS = PytestDeprecationWarning( NO_PRINT_LOGS = PytestDeprecationWarning(