test_ok1/changelog
Bruno Oliveira fd2f172258 Let unittest frameworks deal with async functions
Instead of trying to handle unittest-async functions in pytest_pyfunc_call,
let the unittest framework handle them instead.

This lets us remove the hack in pytest_pyfunc_call, with the upside that
we should support any unittest-async based framework.

Also included 'asynctest' as test dependency for py37-twisted, and renamed
'twisted' to 'unittestextras' to better reflect that we install 'twisted' and
'asynctest' now.

This also fixes the problem of cleanUp functions not being properly called
for async functions.

Fix #7110
Fix #6924
2020-05-01 15:10:28 -03:00
..
4391.improvement.rst Improved time counter used to compute test durations. (#6939) 2020-03-29 15:20:09 +03:00
4583.bugfix.rst Update changelog/4583.bugfix.rst 2020-04-13 14:29:59 +01:00
4677.bugfix.rst Issue 4677 - always relative path in skip report (#6953) 2020-04-17 08:28:36 +03:00
6285.feature.rst Update changelog/6285.feature.rst 2020-03-03 09:59:38 -03:00
6871.bugfix.rst Fix crash when printing while capsysbinary is active 2020-03-16 18:21:33 +02:00
6903.breaking.rst Assume os.dup is always available 2020-03-12 16:47:15 +02:00
6910.bugfix.rst Handle unknown stats in pytest_report_teststatus hook 2020-03-12 20:52:22 -03:00
6924.bugfix.rst prepare tests and disable warnings for asyncio unittest cases 2020-03-30 21:55:12 +02:00
6925.bugfix.rst Fix TerminalRepr instances to be hashable (#6988) 2020-04-03 00:56:53 +02:00
6940.improvement.rst Improved time counter used to compute test durations. (#6939) 2020-03-29 15:20:09 +03:00
6951.bugfix.rst fix #6951: allow to write TerminalReporter.writer 2020-03-30 21:31:53 +02:00
6981.deprecation.rst deprecate the pytest.collect module 2020-03-30 21:53:07 +02:00
6992.bugfix.rst Revert "tmpdir: clean up indirection via config for factories (#6767)" 2020-04-10 07:18:54 +02:00
7061.bugfix.rst Improve error handling around yieldctx fixtures which do not yield a value (#7083) 2020-04-15 12:17:13 +03:00
7097.deprecation.rst fixtures: deprecate pytest._fillfuncargs function 2020-04-24 18:54:46 +03:00
7110.bugfix.rst Let unittest frameworks deal with async functions 2020-05-01 15:10:28 -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.