Releases: pytest-dev/pytest
7.2.2
pytest 7.2.2 (2023-03-03)
Bug Fixes
- #10533: Fixed
pytest.approx{.interpreted-text role="func"} handling of dictionaries containing one or more values of [0.0]{.title-ref}. - #10592: Fixed crash if [--cache-show]{.title-ref} and [--help]{.title-ref} are passed at the same time.
- #10597: Fixed bug where a fixture method named
teardownwould be called as part ofnoseteardown stage. - #10626: Fixed crash if
--fixturesand--helpare passed at the same time. - #10660: Fixed :py
pytest.raises{.interpreted-text role="func"} to return a 'ContextManager' so that type-checkers could narrow
pytest.raises(...) if ... else nullcontext()down to 'ContextManager' rather than 'object'.
Improved Documentation
- #10690: Added [CI]{.title-ref} and [BUILD_NUMBER]{.title-ref} environment variables to the documentation.
- #10721: Fixed entry-points declaration in the documentation example using Hatch.
- #10753: Changed wording of the module level skip to be very explicit
about not collecting tests and not executing the rest of the module.
7.2.1
pytest 7.2.1 (2023-01-13)
Bug Fixes
- #10452: Fix 'importlib.abc.TraversableResources' deprecation warning in Python 3.12.
- #10457: If a test is skipped from inside a fixture, the test summary now shows the test location instead of the fixture location.
- #10506: Fix bug where sometimes pytest would use the file system root directory as
rootdir <rootdir>{.interpreted-text role="ref"} on Windows. - #10607: Fix a race condition when creating junitxml reports, which could occur when multiple instances of pytest execute in parallel.
- #10641: Fix a race condition when creating or updating the stepwise plugin's cache, which could occur when multiple xdist worker nodes try to simultaneously update the stepwise plugin's cache.
7.2.0
pytest 7.2.0 (2022-10-23)
Deprecations
-
#10012: Update
pytest.PytestUnhandledCoroutineWarning{.interpreted-text role="class"} to a deprecation; it will raise an error in pytest 8. -
#10396: pytest no longer depends on the
pylibrary.pytestprovides a vendored copy ofpy.errorandpy.pathmodules but will use thepylibrary if it is installed. If you need otherpy.*modules, continue to install the deprecatedpylibrary separately, otherwise it can usually be removed as a dependency. -
#4562: Deprecate configuring hook specs/impls using attributes/marks.
Instead use :py
pytest.hookimpl{.interpreted-text role="func"} and :pypytest.hookspec{.interpreted-text role="func"}.
For more details, see thedocs <legacy-path-hooks-deprecated>{.interpreted-text role="ref"}. -
#9886: The functionality for running tests written for
nosehas been officially deprecated.This includes:
- Plain
setupandteardownfunctions and methods: this might catch users by surprise, assetup()andteardown()are not pytest idioms, but part of thenosesupport. - Setup/teardown using the @with_setup decorator.
For more details, consult the
deprecation docs <nose-deprecation>{.interpreted-text role="ref"}. - Plain
Features
- #9897: Added shell-style wildcard support to
testpaths.
Improvements
-
#10218:
@pytest.mark.parametrize()(and similar functions) now accepts anySequence[str]for the argument names,
instead of justlist[str]andtuple[str, ...].(Note that
str, which is itself aSequence[str], is still treated as a
comma-delimited name list, as before). -
#10381: The
--no-showlocalsflag has been added. This can be passed directly to tests to override--showlocalsdeclared throughaddopts. -
#3426: Assertion failures with strings in NFC and NFD forms that normalize to the same string now have a dedicated error message detailing the issue, and their utf-8 representation is expresed instead.
-
#7337: A warning is now emitted if a test function returns something other than [None]{.title-ref}. This prevents a common mistake among beginners that expect that returning a [bool]{.title-ref} (for example [return foo(a, b) == result]{.title-ref}) would cause a test to pass or fail, instead of using [assert]{.title-ref}.
-
#8508: Introduce multiline display for warning matching via :py
pytest.warns{.interpreted-text role="func"} and
enhance match comparison for :py_pytest._code.ExceptionInfo.match{.interpreted-text role="func"} as returned by :pypytest.raises{.interpreted-text role="func"}. -
#8646: Improve :py
pytest.raises{.interpreted-text role="func"}. Previously passing an empty tuple would give a confusing
error. We now raise immediately with a more helpful message. -
#9741: On Python 3.11, use the standard library's
tomllib{.interpreted-text role="mod"} to parse TOML.tomli{.interpreted-text role="mod"}` is no longer a dependency on Python 3.11. -
#9742: Display assertion message without escaped newline characters with
-vv. -
#9823: Improved error message that is shown when no collector is found for a given file.
-
#9873: Some coloring has been added to the short test summary.
-
#9883: Normalize the help description of all command-line options.
-
#9920: Display full crash messages in
short test summary info, when runng in a CI environment. -
#9987: Added support for hidden configuration file by allowing
.pytest.inias an alternative topytest.ini.
Bug Fixes
-
#10150:
sys.stdin{.interpreted-text role="data"} now contains all expected methods of a file-like object when capture is enabled. -
#10382: Do not break into pdb when
raise unittest.SkipTest()appears top-level in a file. -
#7792: Marks are now inherited according to the full MRO in test classes. Previously, if a test class inherited from two or more classes, only marks from the first super-class would apply.
When inheriting marks from super-classes, marks from the sub-classes are now ordered before marks from the super-classes, in MRO order. Previously it was the reverse.
When inheriting marks from super-classes, the [pytestmark]{.title-ref} attribute of the sub-class now only contains the marks directly applied to it. Previously, it also contained marks from its super-classes. Please note that this attribute should not normally be accessed directly; use
pytest.Node.iter_markers{.interpreted-text role="func"} instead. -
#9159: Showing inner exceptions by forcing native display in
ExceptionGroupseven when using display options other than--tb=native. A temporary step before full implementation of pytest-native display for inner exceptions inExceptionGroups. -
#9877: Ensure
caplog.get_records(when)returns current/correct data after invokingcaplog.clear().
Improved Documentation
- #10344: Update information on writing plugins to use
pyproject.tomlinstead ofsetup.py. - #9248: The documentation is now built using Sphinx 5.x (up from 3.x previously).
- #9291: Update documentation on how
pytest.warns{.interpreted-text role="func"} affectsDeprecationWarning{.interpreted-text role="class"}.
Trivial/Internal Changes
- #10196:
~pytest.PytestReturnNotNoneWarning{.interpreted-text role="class"} is now a subclass of~pytest.PytestRemovedIn8Warning{.interpreted-text role="class"}: the plan is to make returning non-Nonefrom tests an error in the future. - #10313: Made
_pytest.doctest.DoctestItemexportpytest.DoctestItemfor
type check and runtime purposes. Made [_pytest.doctest]{.title-ref} use internal APIs
to avoid circular imports. - #9906: Made
_pytest.compatre-exportimportlib_metadatain the eyes of type checkers. - #9910: Fix default encoding warning (
EncodingWarning) incacheprovider - #9984: Improve the error message when we attempt to access a fixture that has been
torn down.
Add an additional sentence to the docstring explaining when it's not a good
idea to call getfixturevalue.
7.1.3
pytest 7.1.3 (2022-08-31)
Bug Fixes
- #10060: When running with
--pdb,TestCase.tearDownis no longer called for tests when the class has been skipped viaunittest.skiporpytest.mark.skip. - #10190: Invalid XML characters in setup or teardown error messages are now properly escaped for JUnit XML reports.
- #10230: Ignore
.pyfiles created bypyproject.toml-based editable builds introduced in pip 21.3. - #3396: Doctests now respect the
--import-modeflag. - #9514: Type-annotate
FixtureRequest.paramasAnyas a stop gap measure until8073{.interpreted-text role="issue"} is fixed. - #9791: Fixed a path handling code in
rewrite.pythat seems to work fine, but was incorrect and fails in some systems. - #9917: Fixed string representation for
pytest.approx{.interpreted-text role="func"} when used to compare tuples.
Improved Documentation
- #9937: Explicit note that
tmpdir{.interpreted-text role="fixture"} fixture is discouraged in favour oftmp_path{.interpreted-text role="fixture"}.
Trivial/Internal Changes
- #10114: Replace atomicwrites dependency on windows with [os.replace]{.title-ref}.
7.1.2
pytest 7.1.2 (2022-04-23)
Bug Fixes
- #9726: An unnecessary
numpyimport insidepytest.approx{.interpreted-text role="func"} was removed. - #9820: Fix comparison of
dataclasseswithInitVar. - #9869: Increase
stacklevelfor theNODE_CTOR_FSPATH_ARGdeprecation to point to the
user's code, not pytest. - #9871: Fix a bizarre (and fortunately rare) bug where the [temp_path]{.title-ref} fixture could raise
an internal error while attempting to get the current user's username.
7.1.1
7.1.0
pytest 7.1.0 (2022-03-13)
Breaking Changes
-
#8838: As per our policy, the following features have been deprecated in the 6.X series and are now
removed:pytest._fillfuncargsfunction.pytest_warning_capturedhook - usepytest_warning_recordedinstead.-k -foobarsyntax - use-k 'not foobar'instead.-k foobar:syntax.pytest.collectmodule - import frompytestdirectly.
For more information consult
Deprecations and Removals in the docs. -
#9437: Dropped support for Python 3.6, which reached end-of-life at 2021-12-23.
Improvements
-
#5192: Fixed test output for some data types where
-vwould show less information.Also, when showing diffs for sequences,
-qwould produce full diffs instead of the expected diff. -
#9362: pytest now avoids specialized assert formatting when it is detected that the default
__eq__is overridden inattrsordataclasses. -
#9536: When
-vvis given on command line, show skipping and xfail reasons in full instead of truncating them to fit the terminal width. -
#9644: More information about the location of resources that led Python to raise
ResourceWarning{.interpreted-text role="class"} can now
be obtained by enablingtracemalloc{.interpreted-text role="mod"}.See
resource-warnings{.interpreted-text role="ref"} for more information. -
#9678: More types are now accepted in the
idsargument to@pytest.mark.parametrize.
Previously only [str]{.title-ref}, [float]{.title-ref}, [int]{.title-ref} and [bool]{.title-ref} were accepted;
now [bytes]{.title-ref}, [complex]{.title-ref}, [re.Pattern]{.title-ref}, [Enum]{.title-ref} and anything with a [__name__]{.title-ref} are also accepted. -
#9692:
pytest.approx{.interpreted-text role="func"} now raises aTypeError{.interpreted-text role="class"} when given an unordered sequence (such asset{.interpreted-text role="class"}).Note that this implies that custom classes which only implement
__iter__and__len__are no longer supported as they don't guarantee order.
Bug Fixes
-
#8242: The deprecation of raising
unittest.SkipTest{.interpreted-text role="class"} to skip collection of
tests during the pytest collection phase is reverted - this is now a supported
feature again. -
#9493: Symbolic link components are no longer resolved in conftest paths.
This means that if a conftest appears twice in collection tree, using symlinks, it will be executed twice.
For example, giventests/real/conftest.py
tests/real/test_it.py
tests/link -> tests/realrunning
pytest testsnow imports the conftest twice, once astests/real/conftest.pyand once astests/link/conftest.py.
This is a fix to match a similar change made to test collection itself in pytest 6.0 (see6523{.interpreted-text role="pull"} for details). -
#9626: Fixed count of selected tests on terminal collection summary when there were errors or skipped modules.
If there were errors or skipped modules on collection, pytest would mistakenly subtract those from the selected count.
-
#9645: Fixed regression where
--import-mode=importlibused together withPYTHONPATH{.interpreted-text role="envvar"} orpythonpath{.interpreted-text role="confval"} would cause import errors in test suites. -
#9708:
pytester{.interpreted-text role="fixture"} now requests amonkeypatch{.interpreted-text role="fixture"} fixture instead of creating one internally. This solves some issues with tests that involve pytest environment variables. -
#9730: Malformed
pyproject.tomlfiles now produce a clearer error message.
7.0.1
pytest 7.0.1 (2022-02-11)
Bug Fixes
- #9608: Fix invalid importing of
importlib.readersin Python 3.9. - #9610: Restore [UnitTestFunction.obj]{.title-ref} to return unbound rather than bound method.
Fixes a crash during a failed teardown in unittest TestCases with non-default [__init__]{.title-ref}.
Regressed in pytest 7.0.0. - #9636: The
pythonpathplugin was renamed topython_path. This avoids a conflict with thepytest-pythonpathplugin. - #9642: Fix running tests by id with
::in the parametrize portion. - #9643: Delay issuing a
~pytest.PytestWarning{.interpreted-text role="class"} about diamond inheritance involving~pytest.Item{.interpreted-text role="class"} and
~pytest.Collector{.interpreted-text role="class"} so it can be filtered usingstandard warning filters <warnings>{.interpreted-text role="ref"}.
7.0.0
pytest 7.0.0 (2022-02-03)
(Please see the full set of changes for this release also in the 7.0.0rc1 notes below)
Deprecations
-
#9488: If custom subclasses of nodes like
pytest.Item{.interpreted-text role="class"} override the
__init__method, they should take**kwargs. See
uncooperative-constructors-deprecated{.interpreted-text role="ref"} for details.Note that a deprection warning is only emitted when there is a conflict in the
arguments pytest expected to pass. This deprecation was already part of pytest
7.0.0rc1 but wasn't documented.
Bug Fixes
- #9355: Fixed error message prints function decorators when using assert in Python 3.8 and above.
- #9396: Ensure
pytest.Config.inifile{.interpreted-text role="attr"} is available during thepytest_cmdline_main <_pytest.hookspec.pytest_cmdline_main>{.interpreted-text role="func"} hook (regression during7.0.0rc1).
Improved Documentation
- #9404: Added extra documentation on alternatives to common misuses of [pytest.warns(None)]{.title-ref} ahead of its deprecation.
- #9505: Clarify where the configuration files are located. To avoid confusions documentation mentions
that configuration file is located in the root of the repository.
Trivial/Internal Changes
- #9521: Add test coverage to assertion rewrite path.
pytest 7.0.0rc1 (2021-12-06)
Breaking Changes
-
#7259: The
Node.reportinfo() <non-python tests>{.interpreted-text role="ref"} function first return value type has been expanded from [py.path.local | str]{.title-ref} to [os.PathLike[str] | str]{.title-ref}.Most plugins which refer to [reportinfo()]{.title-ref} only define it as part of a custom
pytest.Item{.interpreted-text role="class"} implementation.
Since [py.path.local]{.title-ref} is a [os.PathLike[str]]{.title-ref}, these plugins are unaffacted.Plugins and users which call [reportinfo()]{.title-ref}, use the first return value and interact with it as a [py.path.local]{.title-ref}, would need to adjust by calling [py.path.local(fspath)]{.title-ref}.
Although preferably, avoid the legacy [py.path.local]{.title-ref} and use [pathlib.Path]{.title-ref}, or use [item.location]{.title-ref} or [item.path]{.title-ref}, instead.Note: pytest was not able to provide a deprecation period for this change.
-
#8246:
--versionnow writes version information tostdoutrather thanstderr. -
#8733: Drop a workaround for pyreadline that made it work with
--pdb.The workaround was introduced in #1281 in 2015, however since then
pyreadline seems to have gone unmaintained, is generating
warnings, and will stop working on Python 3.10. -
#9061: Using
pytest.approx{.interpreted-text role="func"} in a boolean context now raises an error hinting at the proper usage.It is apparently common for users to mistakenly use
pytest.approxlike this:assert pytest.approx(actual, expected)While the correct usage is:
assert actual == pytest.approx(expected)The new error message helps catch those mistakes.
-
#9277: The
pytest.Instancecollector type has been removed.
Importingpytest.Instanceor_pytest.python.Instancereturns a dummy type and emits a deprecation warning.
Seeinstance-collector-deprecation{.interpreted-text role="ref"} for details. -
#9308: PytestRemovedIn7Warning deprecation warnings are now errors by default.
Following our plan to remove deprecated features with as little disruption as
possible, all warnings of typePytestRemovedIn7Warningnow generate errors
instead of warning messages by default.The affected features will be effectively removed in pytest 7.1, so please consult the
deprecations{.interpreted-text role="ref"} section in the docs for directions on how to update existing code.In the pytest
7.0.Xseries, it is possible to change the errors back into warnings as a
stopgap measure by adding this to yourpytest.inifile:[pytest] filterwarnings = ignore::pytest.PytestRemovedIn7WarningBut this will stop working when pytest
7.1is released.If you have concerns about the removal of a specific feature, please add a
comment to9308{.interpreted-text role="issue"}.
Deprecations
-
#7259:
py.path.localarguments for hooks have been deprecated. Seethe deprecation note <legacy-path-hooks-deprecated>{.interpreted-text role="ref"} for full details.py.path.localarguments to Node constructors have been deprecated. Seethe deprecation note <node-ctor-fspath-deprecation>{.interpreted-text role="ref"} for full details.::: {.note}
::: {.admonition-title}
Note
:::The name of the
~_pytest.nodes.Node{.interpreted-text role="class"} arguments and attributes (the
new attribute beingpath) is the opposite of the situation for hooks
(the old argument beingpath).This is an unfortunate artifact due to historical reasons, which should be
resolved in future versions as we slowly get rid of thepy{.interpreted-text role="pypi"}
dependency (see9283{.interpreted-text role="issue"} for a longer discussion).
::: -
#7469: Directly constructing the following classes is now deprecated:
_pytest.mark.structures.Mark_pytest.mark.structures.MarkDecorator_pytest.mark.structures.MarkGenerator_pytest.python.Metafunc_pytest.runner.CallInfo_pytest._code.ExceptionInfo_pytest.config.argparsing.Parser_pytest.config.argparsing.OptionGroup_pytest.pytester.HookRecorder
These constructors have always been considered private, but now issue a deprecation warning, which may become a hard error in pytest 8.
-
#8242: Raising
unittest.SkipTest{.interpreted-text role="class"} to skip collection of tests during the
pytest collection phase is deprecated. Usepytest.skip{.interpreted-text role="func"} instead.Note: This deprecation only relates to using
unittest.SkipTest{.interpreted-text role="class"} during test
collection. You are probably not doing that. Ordinary usage of
unittest.SkipTest{.interpreted-text role="class"} /unittest.TestCase.skipTest{.interpreted-text role="meth"} /
unittest.skip{.interpreted-text role="func"} in unittest test cases is fully supported. -
#8315: Several behaviors of
Parser.addoption <pytest.Parser.addoption>{.interpreted-text role="meth"} are now
scheduled for removal in pytest 8 (deprecated since pytest 2.4.0):parser.addoption(..., help=".. %default ..")- use%(default)sinstead.parser.addoption(..., type="int/string/float/complex")- usetype=intetc. instead.
-
#8447: Defining a custom pytest node type which is both an
pytest.Item <Item>{.interpreted-text role="class"} and apytest.Collector <Collector>{.interpreted-text role="class"} (e.g.pytest.File <File>{.interpreted-text role="class"}) now issues a warning.
It was never sanely supported and triggers hard to debug errors.See
the deprecation note <diamond-inheritance-deprecated>{.interpreted-text role="ref"} for full details. -
#8592:
pytest_cmdline_preparse{.interpreted-text role="hook"} has been officially deprecated. It will be removed in a future release. Usepytest_load_initial_conftests{.interpreted-text role="hook"} instead.See
the deprecation note <cmdline-preparse-deprecated>{.interpreted-text role="ref"} for full details. -
#8645:
pytest.warns(None) <pytest.warns>{.interpreted-text role="func"} is now deprecated because many people used
it to mean "this code does not emit warnings", but it actually had the effect of
checking that the code emits at least one warning of any type - likepytest.warns()
orpytest.warns(Warning). -
#8948:
pytest.skip(msg=...) <pytest.skip>{.interpreted-text role="func"},pytest.fail(msg=...) <pytest.fail>{.interpreted-text role="func"} andpytest.exit(msg=...) <pytest.exit>{.interpreted-text role="func"}
signatures now accept areasonargument instead ofmsg. Usingmsgstill works, but is deprecated and will be removed in a future release.This was changed for consistency with
pytest.mark.skip <pytest.mark.skip>{.interpreted-text role="func"} andpytest.mark.xfail <pytest.mark.xfail>{.interpreted-text role="func"} which both accep...
7.0.0rc1
Prepare release version 7.0.0rc1