test_ok2/changelog
Ran Benita 397769c45e
Merge pull request #11677 from bluetech/nodes-abc
nodes,python: mark abstract node classes as ABCs
2023-12-10 09:41:46 +02:00
..
1531.improvement.rst Improve the full diff by having more consistent indentation in the PrettyPrinter (#11571) 2023-11-27 16:47:18 +02:00
3664.deprecation.rst Update changelog/3664.deprecation.rst 2022-10-10 12:28:14 +01:00
7363.breaking.rst Change PytestRemovedIn8Warning to error by default 2023-06-23 16:42:24 +03:00
7469.feature.rst Export `FixtureDef` 2023-07-15 10:06:06 +03:00
7966.bugfix.rst un-iterable fix 2023-08-20 14:46:09 -07:00
8976.breaking.rst python: change `pytest pkg/__init__.py` to only collect the `__init__.py` Module 2023-06-23 20:42:50 +03:00
9036.bugfix.rst capture warning when exception is raised (fix #9036) 2023-06-30 16:04:37 -07:00
9288.breaking.rst doc: fix some broken Sphinx references 2023-12-07 00:30:35 +02:00
10441.feature.rst Add new `ExceptionInfo.group_contains` assertion helper method 2023-09-17 22:28:32 +01:00
10465.deprecation.rst Change PytestReturnNotNoneWarning to return a normal warning (#11211) 2023-09-07 15:11:59 +00:00
10617.feature.rst Add more comprehensive set assertion rewrites (#11469) 2023-10-02 18:37:52 -03:00
10701.bugfix.rst Apply suggestions from code review 2023-07-04 10:30:19 +02:00
11011.doc.rst add a warning about modifying the root logger during tests 2023-05-18 09:26:16 -05:00
11065.doc.rst Use pytestconfig instead of request.config in cache example (#11542) 2023-10-23 15:45:16 -03:00
11091.doc.rst Use hyphenated cmdline options in docs (#11490) 2023-10-10 21:16:24 +00:00
11122.improvement.rst Switch to new-style pluggy hook wrappers 2023-07-14 22:47:48 +03:00
11137.breaking.rst python: change `Package` to no longer be a `Module`/`File` 2023-07-28 22:49:24 +03:00
11146.bugfix.rst [pre-commit.ci] auto fixes from pre-commit.com hooks 2023-06-26 11:34:03 +00:00
11151.breaking.rst Change PytestReturnNotNoneWarning to return a normal warning (#11211) 2023-09-07 15:11:59 +00:00
11208.trivial.rst fixtures: change `FixtureDef.cached_result[2]` from exception triplet to exception 2023-07-15 10:06:06 +03:00
11216.improvement.rst fixtures: show test as skip location if skipped from an xunit setup function 2023-07-16 23:26:04 +03:00
11218.trivial.rst fixtures: make FixtureRequest abstract, add TopRequest subclass 2023-08-12 11:55:08 +03:00
11227.improvement.rst Have pytest.raises match against exception `__notes__` (#11227) 2023-07-18 08:39:39 -03:00
11255.bugfix.rst fixtures: fix crash when `parametrize(scope="package")` is used without a Package 2023-07-28 16:13:02 +03:00
11277.bugfix.rst python: fix scope assignment for indirect parameter sets (#11277) 2023-08-06 13:59:54 +00:00
11282.breaking.rst Sanitize ini-options default handling #11282 (#11594) 2023-11-11 13:08:18 -03:00
11314.improvement.rst Fixes issue #11314 - log_file_format does not default to log_format (#11444) 2023-09-18 16:50:04 +00:00
11315.trivial.rst pytester: use monkeypatch.chdir() for dir changing 2023-09-25 11:31:09 +03:00
11333.trivial.rst Correct the spelling of ArgSource.INVOCATION_DIR (#11333) 2023-08-23 09:21:17 +00:00
11353.trivial.rst Fixes for typed pluggy 2023-08-26 22:13:24 +03:00
11387.feature.rst Add verbosity_assertions and config.get_verbosity 2023-11-19 11:56:29 -03:00
11447.improvement.rst Change deprecated_call to handle FutureWarning (#11448) 2023-09-18 09:34:05 -03:00
11456.bugfix.rst Duplicated parameters in parametrize marker (#11489) 2023-10-08 10:26:31 -07:00
11520.improvement.rst Separate the various parts of the error report with newlines (#11659) 2023-12-06 09:25:00 +00:00
11563.bugfix.rst Fix crash using empty string for parametrized value more than once 2023-10-27 17:26:12 -03:00
11572.bugfix.rst Fix for operation on closed file in faulthandler teardown (#11584) 2023-11-22 22:05:00 +02:00
11600.improvement.rst Use `False`, instead of `None` as default for `_XfailMarkDecorator`'s `condition` param and update doc (#11600) 2023-11-17 10:42:05 +02:00
11610.feature.rst Add new filtering() method to LogCaptureFixture class (#11625) 2023-11-24 09:38:34 -03:00
11638.trivial.rst Reset color-related envvars for testing (#11638) 2023-11-26 11:09:18 -03:00
11667.breaking.rst Remove `setup.py` 2023-12-04 22:45:59 +02:00
11676.breaking.rst nodes,python: mark abstract node classes as ABCs 2023-12-07 16:41:07 +02:00
README.rst Use hyphenated cmdline options in docs (#11490) 2023-10-10 21:16:24 +00: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 ``--junit-xml``, 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.