test_ok2/changelog
Bruno Oliveira e38d1cac48 Improve error message for malformed pyproject.toml files
Including the file name is enough to let the user know what the problem is.

The same is not needed for `.ini` files because the error message includes the path to the file by default.

Fix #9730
2022-03-05 08:59:28 -03:00
..
5192.improvement.rst Fix diff output for data types where `-v` would show less information (#9661) 2022-02-15 09:43:20 -03:00
8242.bugfix.rst Revert "Deprecate raising unittest.SkipTest to skip tests during collection" (#9710) 2022-02-23 15:59:54 +02:00
8838.breaking.rst Remove `PytestRemovedIn7Warning` 2021-12-08 15:58:08 +02:00
9362.improvement.rst Fix numbering and improve changelog entry for #9362 (#9713) 2022-02-23 19:03:13 -03:00
9437.breaking.rst Drop Python3.6 in CI, setup.cfg, and readme. 2021-12-26 21:08:37 +01:00
9493.bugfix.rst config: stop resolving symlinks in conftest paths 2022-01-09 12:33:45 +02:00
9536.improvement.rst With -vv, display the full skip/xfail reason instead of "..." (#9537) 2022-01-25 10:33:22 -03:00
9626.bugfix.rst Fix count of selected tests on terminal collection summary (#9628) 2022-02-15 11:17:34 +00:00
9644.improvement.rst Expand warnings output for ResourceWarning (#9682) 2022-02-15 13:00:50 +00:00
9645.bugfix.rst Try to import module before creating dummy modules with 'importmode=importlib' 2022-02-14 09:42:05 -03:00
9678.improvement.rst python: unify code to generate ID from value 2022-02-12 19:22:37 +02:00
9692.improvement.rst Disallow unordered sequences in pytest.approx (#9709) 2022-02-24 10:16:35 -03:00
9708.bugfix.rst pytester now requests monkeypatch instead of creating its own instance 2022-03-04 08:58:44 -05:00
9730.bugfix.rst Improve error message for malformed pyproject.toml files 2022-03-05 08:59:28 -03:00
README.rst docs: use doc/en/_build/html for html output (#6842) 2020-02-29 00:47:30 +01: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 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/html/changelog.html``) if you want to get a preview of how your change will look in the final release notes.