test_ok2/changelog
Ran Benita 14890329dc config: fix the paths considered for initial conftest discovery
Fixes #11104.

See the issue for a description of the problem.

Now, we use the same logic for initial conftest paths as we do for
deciding the initial args, which was the idea behind checking
`namespace.file_or_dir` and `testpaths` previously.

This fixes the issue of `testpaths` being considered for initial
conftests even when it's not used for the args.

(Another issue in faeb16146b was that the
`testpaths` were not glob-expanded, this is also fixed.)
2023-06-21 09:01:42 +03:00
..
1904.bugfix.rst nodes: apply same traceback filtering for chained exceptions as main exception 2023-05-28 17:20:50 +03:00
8711.improvement.rst Handle disabled logging in 'caplog.set_level' and 'caplog.at_level' (#8758) 2023-05-18 10:18:59 -03:00
9146.doc.rst Update 9146.doc.rst 2021-10-01 21:33:32 +05:30
10831.bugfix.rst Fix `pytrace=False` and `--tb=line` reports `None` (#10905) 2023-04-16 20:31:45 +00:00
10872.improvement.rst Use NamedTuple for pytest_report_teststatus return value (#10972) 2023-05-19 08:24:28 -03:00
10901.feature.rst code: add ExceptionInfo.from_exception 2023-04-12 13:16:48 +03:00
10907.improvement.rst doc: add missing changelog for #10907 2023-04-16 18:22:51 +03:00
10940.improvement.rst Improve verbose output by wrapping skip/xfail reasons with margin (#10958) 2023-05-06 12:15:11 -03:00
10991.improvement.rst Handle microseconds with custom logging.Formatter (#11047) 2023-05-30 09:35:33 -03:00
11005.improvement.rst Include reason in cache path warnings to aid debugging (#11005) 2023-05-18 10:11:47 -03:00
11013.improvement.rst Add warning when testpaths is set but paths are not found by glob (#11044) 2023-05-30 07:06:13 -03:00
11031.trivial.rst Add alias `--config-file` to `-c` (#11036) 2023-05-26 07:56:18 -03:00
11043.improvement.rst config: fallback confcutdir to rootpath if inipath is not set 2023-05-30 19:52:59 +03:00
11068.bugfix.rst cacheprovider: make file-skipping work with any File, not just Modules 2023-06-03 09:32:26 +03:00
11081.improvement.rst changelog: add note to `norecursedir`/`pytest_ignore_collect` change (#11095) 2023-06-10 19:34:59 +00:00
11104.bugfix.rst config: fix the paths considered for initial conftest discovery 2023-06-21 09:01:42 +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.