Remove stale CHANGELOG entries
Those were not removed in the last release because of a bug in towncrier; I was about to fallback to don't use the .rst extension for entries but just noticed that this was fixed in towncrier 17.8.0 so it should no longer be a problem.
This commit is contained in:
parent
beacecf29b
commit
e5eba8419a
|
@ -1 +0,0 @@
|
|||
New ``--show-capture`` command-line option that allows to specify how to display captured output when tests fail: ``no``, ``stdout``, ``stderr``, ``log`` or ``all`` (the default).
|
|
@ -1 +0,0 @@
|
|||
New ``--rootdir`` command-line option to override the rules for discovering the root directory. See `customize <https://docs.pytest.org/en/latest/customize.html>`_ in the documentation for details.
|
|
@ -1 +0,0 @@
|
|||
Added a `reference <https://docs.pytest.org/en/latest/reference.html>`_ page to the docs.
|
|
@ -1 +0,0 @@
|
|||
Suppress ``IOError`` when closing the temporary file used for capturing streams in Python 2.7.
|
|
@ -1 +0,0 @@
|
|||
Fixtures are now instantiated based on their scopes, with higher-scoped fixtures (such as ``session``) being instantiated first than lower-scoped fixtures (such as ``function``). The relative order of fixtures of the same scope is kept unchanged, based in their declaration order and their dependencies.
|
|
@ -1,2 +0,0 @@
|
|||
``record_xml_property`` renamed to ``record_property`` and is now compatible with xdist, markers and any reporter.
|
||||
``record_xml_property`` name is now deprecated.
|
|
@ -1 +0,0 @@
|
|||
``record_xml_property`` fixture is now deprecated in favor of the more generic ``record_property``.
|
|
@ -1 +0,0 @@
|
|||
New ``--nf``, ``--new-first`` options: run new tests first followed by the rest of the tests, in both cases tests are also sorted by the file modified time, with more recent files coming first.
|
|
@ -1 +0,0 @@
|
|||
Defining ``pytest_plugins`` is now deprecated in non-top-level conftest.py files, because they "leak" to the entire directory tree.
|
|
@ -1 +0,0 @@
|
|||
New ``--last-failed-no-failures`` command-line option that allows to specify the behavior of the cache plugin's ```--last-failed`` feature when no tests failed in the last run (or no cache was found): ``none`` or ``all`` (the default).
|
|
@ -1 +0,0 @@
|
|||
New ``--doctest-continue-on-failure`` command-line option to enable doctests to show multiple failures for each snippet, instead of stopping at the first failure.
|
|
@ -1 +0,0 @@
|
|||
Captured log messages are added to the ``<system-out>`` tag in the generated junit xml file if the ``junit_logging`` ini option is set to ``system-out``. If the value of this ini option is ``system-err`, the logs are written to ``<system-err>``. The default value for ``junit_logging`` is ``no``, meaning captured logs are not written to the output file.
|
|
@ -1 +0,0 @@
|
|||
Allow the logging plugin to handle ``pytest_runtest_logstart`` and ``pytest_runtest_logfinish`` hooks when live logs are enabled.
|
|
@ -1 +0,0 @@
|
|||
Passing `--log-cli-level` in the command-line now automatically activates live logging.
|
|
@ -1 +0,0 @@
|
|||
Add command line option ``--deselect`` to allow deselection of individual tests at collection time.
|
|
@ -1 +0,0 @@
|
|||
Captured logs are printed before entering pdb.
|
|
@ -1 +0,0 @@
|
|||
Deselected item count is now shown before tests are run, e.g. ``collected X items / Y deselected``.
|
|
@ -1 +0,0 @@
|
|||
Change minimum requirement of ``attrs`` to ``17.4.0``.
|
|
@ -1 +0,0 @@
|
|||
The builtin module ``platform`` is now available for use in expressions in ``pytest.mark``.
|
|
@ -1 +0,0 @@
|
|||
Renamed example directories so all tests pass when ran from the base directory.
|
|
@ -1 +0,0 @@
|
|||
Remove usage of deprecated ``metafunc.addcall`` in our own tests.
|
|
@ -1 +0,0 @@
|
|||
Internal ``mark.py`` module has been turned into a package.
|
|
@ -1 +0,0 @@
|
|||
The *short test summary info* section now is displayed after tracebacks and warnings in the terminal.
|
|
@ -1 +0,0 @@
|
|||
``pytest`` now depends on the `more_itertools <https://github.com/erikrose/more-itertools>`_ package.
|
|
@ -1 +0,0 @@
|
|||
Added warning when ``[pytest]`` section is used in a ``.cfg`` file passed with ``-c``
|
|
@ -1 +0,0 @@
|
|||
``nodeids`` can now be passed explicitly to ``FSCollector`` and ``Node`` constructors.
|
|
@ -1 +0,0 @@
|
|||
Internal refactoring of ``FormattedExcinfo`` to use ``attrs`` facilities and remove old support code for legacy Python versions.
|
|
@ -1 +0,0 @@
|
|||
New ``--verbosity`` flag to set verbosity level explicitly.
|
|
@ -1 +0,0 @@
|
|||
Refactoring to unify how verbosity is handled internally.
|
|
@ -1,2 +0,0 @@
|
|||
Fixed ``clear()`` method on ``caplog`` fixture which cleared ``records``,
|
||||
but not the ``text`` property.
|
|
@ -1 +0,0 @@
|
|||
Internal refactoring to better integrate with argparse.
|
|
@ -1 +0,0 @@
|
|||
Fix a python example when calling a fixture in doc/en/usage.rst
|
|
@ -1 +0,0 @@
|
|||
``pytest.approx`` now accepts comparing a numpy array with a scalar.
|
|
@ -1,3 +0,0 @@
|
|||
During test collection, when stdin is not allowed to be read, the
|
||||
``DontReadFromStdin`` object still allow itself to be iterable and
|
||||
resolved to an iterator without crashing.
|
Loading…
Reference in New Issue