test_ok2

History

Ran Benita 310b67b227 Drop attrs dependency, use dataclasses instead (#10669 ) Since pytest now requires Python>=3.7, we can use the stdlib attrs clone, dataclasses, instead of the OG package. attrs is still somewhat nicer than dataclasses and has some extra functionality, but for pytest usage there's not really a justification IMO to impose the extra dependency on users when a standard alternative exists.		2023-01-20 11:13:36 +02:00
..
6267.improvement.rst	Avoid truncation when truncating means longer output (#10446 )	2022-12-17 10:24:46 -03:00
7431.feature.rst	Add --log-disable CLI option (#10371 )	2022-10-23 18:23:34 -03:00
8141.feature.rst	Change the default policy to all	2022-12-25 00:18:38 +09:00
10226.improvement.rst	Use exceptiongroup for teardown errors	2022-10-23 15:45:50 -07:00
10525.feature.rst	Class methods can now be discovered as tests (#10552 )	2022-12-02 15:53:04 +00:00
10592.bugfix.rst	Fix crash if `--cache-show` and `--help` are passed at the same time	2023-01-19 09:44:57 -03:00
10660.bugfix.rst	Derive pytest.raises from AbstractContextManager	2023-01-13 13:58:49 -05:00
10669.trivial.rst	Drop attrs dependency, use dataclasses instead (#10669 )	2023-01-20 11:13:36 +02: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.