test_ok2

History

Ran Benita afaabdda8c cacheprovider: fix some files in packages getting lost from --lf --lf has an optimization where it skips collecting Modules (python files) which don't contain failing tests. The optimization works by getting the paths of all cached failed tests and skipping the collection of Modules whose path is not included in that list. In pytest, Package nodes are Module nodes with the fspath being the file `<package dir>/__init__.py`. Since it's a Module the logic above triggered for it, and because it's an `__init__.py` file which is unlikely to have any failing tests in it, it is skipped, which causes its entire directory to be skipped, including any Modules inside it with failing tests. Fix by special-casing Packages to never filter. This means entire Packages are never filtered, the Modules themselves are always checked. It is reasonable to consider an optimization which does filter entire packages bases on parent paths etc. but this wouldn't actually save any real work so is really not worth it.		2020-10-19 19:02:43 +03:00
..
7425.feature.rst	New pytester fixture (#7854 )	2020-10-12 12:13:06 -03:00
7710.improvement.rst	python_api: let approx() take nonnumeric values (#7710 )	2020-09-28 12:17:23 -03:00
7758.bugfix.rst	cacheprovider: fix some files in packages getting lost from --lf	2020-10-19 19:02:43 +03:00
7780.doc.rst	doc: patch Sphinx to detect our `@final` for marking classes as `final`	2020-10-03 13:13:14 +03:00
7802.trivial.rst	Bump attrs requirement from >=17.4.0 to >=19.2.0	2020-09-27 13:17:59 +03:00
7808.breaking.rst	py36+: drop python3.5 in CI and setup.cfg	2020-10-02 14:00:11 -07:00
7815.doc.rst	Add alias clarification to deprecation warning (#7829 )	2020-10-06 11:48:34 -03:00
7872.doc.rst	Added changelog/7872.doc.rst	2020-10-07 18:06:13 -04:00
7878.doc.rst	ask for commit after changelog and authors file edit (#7878 )	2020-10-09 16:10:54 +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.