diff --git a/docs/overview.rst b/docs/overview.rst index d230a1d3da..08b3da85ef 100644 --- a/docs/overview.rst +++ b/docs/overview.rst @@ -755,7 +755,8 @@ Matej Focko, Yulia Kopkova, Tomáš Bajer, Carlos Rodriguez-Fernandez, James Molet, Cristian Le, Lili Nie, Martin Čermák, Michael Vogt, Qinghua Cheng, Michael Engel, Anatoli Babenia, Colin Walters, Link Dupont, Mario Casquero, Martin Klusoň, Pavel Holica, -Otto Šabart, Ismail Ibrahim Quwarah and Sergei Petrosian. +Otto Šabart, Ismail Ibrahim Quwarah, Sergei Petrosian, Tom +Koscielniak and Han Han. Copyright diff --git a/docs/releases.rst b/docs/releases.rst index 0b62eec8f3..c270cb6e0b 100644 --- a/docs/releases.rst +++ b/docs/releases.rst @@ -12,64 +12,67 @@ to gather early feedback from users about the way how issues are linked with newly created and existing tests and plans. See the :ref:`link-issues` section for details about the configuration. -The :ref:`/plugins/report/polarion` report plugin now uses Jinja template to -generate the XUnit file. It doesn't do any extra modifications to the XML tree -using an ``ElementTree`` anymore. Also the schema is now validated against the -XSD. - -The values in the generated ``tmt-report-results.yaml`` file are -now wrapped in double quotes, and any double quotes within the -values are escaped to ensure that the resulting file is always -valid YAML. - -The :ref:`/plugins/report/junit` report plugin now validates all the XML -flavors against their respective XSD schemas and tries to prettify the final -XML output. These functionalities are always disabled for ``custom`` flavors. -The prettify functionality can be controlled for non-custom templates by -``--prettify`` and ``--no-prettify`` arguments. - -The :ref:`/plugins/report/junit` report plugin now uses Jinja instead of -``junit-xml`` library to generate the JUnit XMLs. It also adds support for a -new ``--flavor`` argument. Using this argument the user can choose between a -``default`` flavor, which keeps the current behavior untouched, and a -``custom`` flavor where user must provide a custom template using a -``--template-path`` argument. - -The ``fmf-id.ref`` will now try to report the most human-readable committish -reference, either branch, tag, git-describe, or if all fails the commit hash. -You may encounter this in the verbose log of ``tmt tests show`` or plan/test -imports. - -:ref:`Result specification` now defines -``original-result`` key holding the original outcome of a test, subtest -or test checks. The effective outcome, stored in ``result`` key, is -computed from the original outcome, and it is affected by inputs like -:ref:`test result interpretation` or -:ref:`test checks`. - -In verbose mode, the ``discover`` step now prints information -about the beakerlib libraries which were fetched for the test -execution. Use ``tmt run discover -vvv`` to see the details. - The ``tmt try`` command now supports the new :ref:`/stories/cli/try/option/epel` option backed by the :ref:`prepare/feature` plugin and the new :ref:`/stories/cli/try/option/install` option backed by the :ref:`prepare/feature` plugin. +In verbose mode, the ``discover`` step now prints information +about the beakerlib libraries which were fetched for the test +execution. Use ``tmt run discover -vvv`` to see the details. + +The :ref:`/plugins/provision/beaker` provision plugin now newly +supports providing a custom :ref:`/spec/plans/provision/kickstart` +configuration. + The new key :ref:`/spec/hardware/iommu` allowing to provision a guest with the `Input–output memory management unit` has been added into the :ref:`/spec/hardware` specification and implemented in the :ref:`/plugins/provision/beaker` provision plugin. -The :ref:`/plugins/provision/beaker` provision plugin now newly -supports providing a custom :ref:`/spec/plans/provision/kickstart` -configuration. +The :ref:`/plugins/report/junit` report plugin now validates all +the XML flavors against their respective XSD schemas and tries to +prettify the final XML output. These functionalities are always +disabled for ``custom`` flavors. The prettify functionality can +be controlled for non-custom templates by ``--prettify`` and +``--no-prettify`` arguments. + +The :ref:`/plugins/report/junit` report plugin now uses Jinja +instead of ``junit-xml`` library to generate the JUnit XMLs. It +also adds support for a new ``--flavor`` argument. Using this +argument the user can choose between a ``default`` flavor, which +keeps the current behavior untouched, and a ``custom`` flavor +where user must provide a custom template using a +``--template-path`` argument. + +The :ref:`/plugins/report/polarion` report plugin now uses Jinja +template to generate the XUnit file. It doesn't do any extra +modifications to the XML tree using an ``ElementTree`` anymore. +Also the schema is now validated against the XSD. The :ref:`/plugins/report/reportportal` plugin now uploads the complete set of discovered tests, including those which have not been executed. These tests are marked as ``skipped``. +The ``fmf-id.ref`` will now try to report the most human-readable +committish reference, either branch, tag, git-describe, or if all +fails the commit hash. You may encounter this in the verbose log +of ``tmt tests show`` or plan/test imports. + +:ref:`Result specification` now defines +``original-result`` key holding the original outcome of a test, +subtest or test checks. The effective outcome, stored in +``result`` key, is computed from the original outcome, and it is +affected by inputs like :ref:`test result +interpretation` or :ref:`test +checks`. + +The values in the generated ``tmt-report-results.yaml`` file are +now wrapped in double quotes, and any double quotes within the +values are escaped to ensure that the resulting file is always +valid YAML. + tmt-1.36.1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~