test_ok1

History

Ran Benita 25e657bfc1 Deprecate raising unittest.SkipTest to skip tests during collection It is not very clear why this code exists -- we are not running any unittest or nose code during collection, and really these frameworks don't have the concept of collection at all, and just raising these exceptions at e.g. the module level would cause an error. So unless I'm missing something, I don't think anyone is using this. Deprecate it so we can eventually clear up this code and keep unittest more tightly restricted to its plugin.		2021-01-15 00:05:33 +02:00
..
7469.deprecation.rst	runner: export pytest.CallInfo for typing purposes	2020-12-26 21:38:37 +02:00
7469.feature.rst	runner: export pytest.CallInfo for typing purposes	2020-12-26 21:38:37 +02:00
8061.bugfix.rst	Fix failing staticmethod tests if they are inherited (#8205 )	2020-12-30 19:00:37 -08:00
8144.feature.rst	hookspec: add pathlib.Path alternatives to py.path.local parameters in hooks	2020-12-15 00:34:23 +02:00
8152.bugfix.rst	terminal: fix "(<Skipped instance>)" skip reason in test status line	2020-12-15 22:24:25 +02:00
8174.trivial.rst	Convert most of the collection code from py.path to pathlib	2020-12-22 21:09:36 +02:00
8192.bugfix.rst	Add dot prefix if file makefile extension is invalid for pathlib (#8222 )	2021-01-04 15:58:11 +02:00
8242.deprecation.rst	Deprecate raising unittest.SkipTest to skip tests during collection	2021-01-15 00:05:33 +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.