test_ok2/changelog
Daniel Hahler 1356d20e90 Merge master into features 2020-01-10 05:20:41 +01:00
..
449.improvement.rst terminal: use "yellow" with any "xpassed" tests 2020-01-09 22:20:41 +01:00
759.improvement.rst parametrized: ids: support generator/iterator 2019-11-20 19:02:17 +01:00
1857.improvement.rst parametrized: ids: support generator/iterator 2019-11-20 19:02:17 +01:00
3238.deprecation.rst Deprecate --no-print-logs option 2019-12-14 16:46:30 -08:00
3823.bugfix.rst unittest: do not use TestCase.debug() with `--pdb` 2019-11-10 00:21:51 +01:00
4445.bugfix.rst Add stacklevel tests for warnings, 'location' to pytest_warning_captured 2019-11-22 17:50:00 -03:00
4597.feature.rst Include new --capture-mode=tee-sys option 2019-12-09 13:05:23 -03:00
4639.improvement.rst Preparing release version 5.3.2 2019-12-13 08:51:15 -03:00
5686.improvement.rst fix #5686, mktemp now fails given absolute and non-normalized paths. 2019-12-12 13:00:23 +01:00
5928.bugfix.rst Add stacklevel tests for warnings, 'location' to pytest_warning_captured 2019-11-22 17:50:00 -03:00
5971.bugfix.rst Fix serialization of 'None' reprcrashes 2020-01-06 22:04:38 -03:00
5975.deprecation.rst deprecate direct node construction and introduce Node.from_parent 2019-11-23 21:54:11 +01:00
5984.improvement.rst Add stacklevel tests for warnings, 'location' to pytest_warning_captured 2019-11-22 17:50:00 -03:00
5991.bugfix.rst unittest: do not use TestCase.debug() with `--pdb` 2019-11-10 00:21:51 +01:00
6213.improvement.rst pytester: remove special handling of env during inner runs 2019-11-22 21:50:31 +01:00
6247.improvement.rst Respect --fulltrace with collection errors 2019-11-20 23:35:33 +01:00
6316.breaking.rst Replace 'removal' by 'breaking' changelog category 2019-12-06 08:50:35 -03:00
6334.bugfix.rst Add CHANGELOG entry for #6334 2019-12-12 08:05:22 -03:00
6350.trivial.rst Optimized renaming of test parameter ids 2019-12-16 18:53:48 -03:00
6404.trivial.rst Remove usage of parser module, deprecated in Python 3.9 2020-01-06 08:57:07 -03:00
6532.bugfix.rst Fix `RunResult.parseoutcomes` (follow-up to #6353) 2019-12-30 17:08:52 +01:00
README.rst Replace 'removal' by 'breaking' changelog category 2019-12-06 08:50:35 -03:00
_template.rst Update CHANGELOG template to put issue links at the start of entries 2018-07-07 11:02:33 -03:00

README.rst

This directory contains "newsfragments" which are short files that contain a small **ReST**-formatted
text that will be added to the next ``CHANGELOG``.

The ``CHANGELOG`` will be read by **users**, so this description should be aimed to pytest users
instead of describing internal changes which are only relevant to the developers.

Make sure to use full sentences in the **past or present tense** and use punctuation, examples::

    Improved verbose diff output with sequences.

    Terminal summary statistics now use multiple colors.

Each file should be named like ``<ISSUE>.<TYPE>.rst``, where
``<ISSUE>`` is an issue number, and ``<TYPE>`` is one of:

* ``feature``: new user facing features, like new command-line options and new behavior.
* ``improvement``: improvement of existing functionality, usually without requiring user intervention (for example, new fields being written in ``--junitxml``, improved colors in terminal, etc).
* ``bugfix``: fixes a reported bug.
* ``doc``: documentation improvement, like rewording an entire session or adding missing docs.
* ``deprecation``: feature deprecation.
* ``breaking``: a change which may break existing suites, such as feature removal or behavior change.
* ``vendor``: changes in packages vendored in pytest.
* ``trivial``: fixing a small typo or internal change that might be noteworthy.

So for example: ``123.feature.rst``, ``456.bugfix.rst``.

If your PR fixes an issue, use that number here. If there is no issue,
then after you submit the PR and get the PR number you can add a
changelog using that instead.

If you are not sure what issue type to use, don't hesitate to ask in your PR.

``towncrier`` preserves multiple paragraphs and formatting (code blocks, lists, and so on), but for entries
other than ``features`` it is usually better to stick to a single paragraph to keep it concise.

You can also run ``tox -e docs`` to build the documentation
with the draft changelog (``doc/en/_build/changelog.html``) if you want to get a preview of how your change will look in the final release notes.