8000
trusted-contributions-gcf
bot
added
the
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
label
Aug 27, 2020
google-cla
bot
added
the
cla: yes
This human has signed the Contributor License Agreement.
label
Aug 27, 2020
kokoro-team
removed
the
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
label
Aug 27, 2020
product-auto-label
bot
added
the
samples
Issues that are directly related to samples.
label
Aug 27, 2020
renovate-bot
force-pushed
the
renovate/pytest-6.x
branch
from
August 27, 2020 18:04
renovate-bot
changed the title
chore(deps): update dependency pytest to v6.0.1
Update dependency pytest to v6.0.1
Aug 27, 2020
trusted-contributions-gcf
bot
added
the
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
label
Aug 27, 2020
kokoro-team
removed
the
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
label
Aug 27, 2020
renovate-bot
changed the title
Update dependency pytest to v6.0.1
chore(deps): update dependency pytest to v6.0.1
Aug 28, 2020
renovate-bot
changed the title
chore(deps): update dependency pytest to v6.0.1
Update dependency pytest to v6.0.1
Aug 28, 2020
renovate-bot
changed the title
Update dependency pytest to v6.0.1
chore(deps): update dependency pytest to v6.0.1
Aug 28, 2020
chore(deps): update dependency pytest to v6.0.1 #4567
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
busunkim96
approved these changes
Aug 27, 2020
leahecole
approved these changes
Aug 27, 2020
0f15c6e to
21db53c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==5.3.2->==6.0.1==6.0.0->==6.0.1Release Notes
pytest-dev/pytest
v6.0.1Compare Source
pytest 6.0.1 (2020-07-30)
Bug Fixes
helpvalue toParser.add_optionis now accepted instead of crashing when runningpytest --help.Passing
Noneraises a more informativeTypeError.not-callablelint onpytest.mark.parametrize()and the other builtin marks:skip,skipif,xfail,usefixtures,filterwarnings.TestReport.longreprtext(such aspytest-html) whenTestReport.longrepris not a string.caplog.set_level().v6.0.0Compare Source
pytest 6.0.0 (2020-07-28)
(Please see the full set of changes for this release also in the 6.0.0rc1 notes below)
Breaking Changes
#5584: PytestDeprecationWarning are now errors by default.
Following our plan to remove deprecated features with as little disruption as
possible, all warnings of type
PytestDeprecationWarningnow generate errorsinstead of warning messages.
The affected features will be effectively removed in pytest 6.1, so please consult the
Deprecations and Removals
section in the docs for directions on how to update existing code.
In the pytest
6.0.Xseries, it is possible to change the errors back into warnings as astopgap measure by adding this to your
pytest.inifile:But this will stop working when pytest
6.1is released.If you have concerns about the removal of a specific feature, please add a
comment to #5584.
#7472: The
exec_()andis_true()methods of_pytest._code.Framehave been removed.Features
Improvements
--log-fileCLI option andlog_fileini marker now create subdirectories if needed.matchequals the obtained string but is not a regex match. In this case it is suggested to escape the regex.Bug Fixes
@pytest.mark.skipwhen--runxfailis used.stale temporary directories is not accessible.
capfd.TracebackEntry.__str__which was changed by accident.Improved Documentation
usefixturesmark can apply fixtures to test.-qoption used in getting started guide.Trivial/Internal Changes
packageis no longer considered experimental.pytest 6.0.0rc1 (2020-07-08)
Breaking Changes
#1316:
TestReport.longrepris now always an instance ofReprExceptionInfo. Previously it was astrwhen a test failed withpytest.fail(..., pytrace=False).#5965: symlinks are no longer resolved during collection and matching conftest.py files with test file paths.
Resolving symlinks for the current directory and during collection was introduced as a bugfix in 3.9.0, but it actually is a new feature which had unfortunate consequences in Windows and surprising results in other platforms.
The team decided to step back on resolving symlinks at all, planning to review this in the future with a more solid solution (see discussion in
#6523 for details).
This might break test suites which made use of this feature; the fix is to create a symlink
for the entire test tree, and not only to partial files/tress as it was possible previously.
#6505:
Testdir.run().parseoutcomes()now always returns the parsed nouns in plural form.Originally
parseoutcomes()would always returns the nouns in plural form, but a changemeant to improve the terminal summary by using singular form single items (
1 warningor1 error)caused an unintended regression by changing the keys returned by
parseoutcomes().Now the API guarantees to always return the plural form, so calls like this:
Need to be changed to:
#6903: The
os.dup()function is now assumed to exist. We are not aware of anysupported Python 3 implementations which do not provide it.
#7040:
-kno longer matches against the names of the directories outside the test session root.Also,
pytest.Package.nameis now just the name of the directory containing the package's__init__.pyfile, instead of the full path. This is consistent with how the other nodesare named, and also one of the reasons why
-kwould match against any directory containingthe test suite.
#7122: Expressions given to the
-mand-koptions are no longer evaluated using Python's eval.The format supports
or,and,not, parenthesis and general identifiers to match against.Python constants, keywords or other operators are no longer evaluated differently.
#7135: Pytest now uses its own
TerminalWriterclass instead of using the one from thepylibrary.Plugins generally access this class through
TerminalReporter.writer,TerminalReporter.write()(and similar methods), or
_pytest.config.create_terminal_writer().The following breaking changes were made:
write()method and others) no longer flush implicitly; the flushing behaviorof the underlying file is respected. To flush explicitly (for example, if you
want output to be shown before an end-of-line is printed), use
write(flush=True)orterminal_writer.flush().byteswas removed.relinemethod andchars_on_current_lineproperty were removed.stringioandencodingarguments was removed.#7224: The item.catch_log_handler and item.catch_log_handlers attributes, set by the
logging plugin and never meant to be public , are no longer available.
The deprecated
--no-print-logsoption is removed. Use--show-captureinstead.#7226: Removed the unused
argsparameter frompytest.Function.__init__.#7418: Removed the pytest_doctest_prepare_content hook specification. This hook
hasn't been triggered by pytest for at least 10 years.
#7438: Some changes were made to the internal
_pytest._code.source, listed herefor the benefit of plugin authors who may be using it:
deindentargument toSource()has been removed, now it is always true.Source()has been removed.Sourcewith anstrhas been removed.Source.isparseable()andSource.putaround()have been removed.Source.compile()and function_pytest._code.compile()havebeen removed; use plain
compile()instead._pytest._code.source.getsource()has been removed; useSource()directly instead.Deprecations
#7210: The special
-k '-expr'syntax to-kis deprecated. Use-k 'not expr'instead.
The special
-k 'expr:'syntax to-kis deprecated. Please open an issueif you use this and want a replacement.
#4049:
pytest_warning_capturedis deprecated in favor of thepytest_warning_recordedhook.Features
#1556: pytest now supports
pyproject.tomlfiles for configuration.The configuration options is similar to the one available in other formats, but must be defined
in a
[tool.pytest.ini_options]table to be picked up by pytest:pyproject.toml
#3342: pytest now includes inline type annotations and exposes them to user programs.
Most of the user-facing API is covered, as well as internal code.
If you are running a type checker such as mypy on your tests, you may start
noticing type errors indicating incorrect usage. If you run into an error that
you believe to be incorrect, please let us know in an issue.
The types were developed against mypy version 0.780. Versions before 0.750
are known not to work. We recommend using the latest version. Other type
checkers may work as well, but they are not officially verified to work by
pytest yet.
#4049: Introduced a new hook named pytest_warning_recorded to convey information about warnings captured by the internal pytest warnings plugin.
This hook is meant to replace pytest_warning_captured, which is deprecated and will be removed in a future release.
#6471: New command-line flags:
#6856: A warning is now shown when an unknown key is read from a config INI file.
The --strict-config flag has been added to treat these warnings as errors.
#6906: Added --code-highlight command line option to enable/disable code highlighting in terminal output.
#7245: New
--import-mode=importliboption that uses importlib to import test modules.Traditionally pytest used
__import__while changingsys.pathto import test modules (whichalso changes
sys.modulesas a side-effect), which works but has a number of drawbacks, like requiring test modulesthat don't live in packages to have unique names (as they need to reside under a unique name in
sys.modules).--import-mode=importlibuses more fine grained import mechanisms fromimportlibwhich don'trequire pytest to change
sys.pathorsys.modulesat all, eliminating much of the drawbacksof the previous mode.
We intend to make
--import-mode=importlibthe default in future versions, so users are encouragedto try the new mode and provide feedback (both positive or negative) in issue #7245.
You can read more about this option in the documentation.
#7305: New
required_pluginsconfiguration option allows the user to specify a list of plugins, including version information, that are required for pytest to run. An error is raised if any required plugins are not found when running pytest.Improvements
#4375: The
pytestcommand now suppresses theBrokenPipeErrorerror message thatis printed to stderr when the output of
pytestis piped and and the pipe isclosed by the piped-to program (common examples are
lessandhead).#4391: Improved precision of test durations measurement.
CallInfoitems now have a new<CallInfo>.durationattribute, created usingtime.perf_counter(). This attribute is used to fill the<TestReport>.durationattribute, which is more accurate than the previous<CallInfo>.stop - <CallInfo>.start(as these are based ontime.time()).#4675: Rich comparison for dataclasses and attrs-classes is now recursive.
#6285: Exposed the pytest.FixtureLookupError exception which is raised by request.getfixturevalue()
(where request is a FixtureRequest fixture) when a fixture with the given name cannot be returned.
#6433: If an error is encountered while formatting the message in a logging call, for
example
logging.warning("oh no!: %s: %s", "first")(a second argument ismissing), pytest now propagates the error, likely causing the test to fail.
Previously, such a mistake would cause an error to be printed to stderr, which
is not displayed by default for passing tests. This change makes the mistake
visible during testing.
You may supress this behavior temporarily or permanently by setting
logging.raiseExceptions = False.#6817: Explicit new-lines in help texts of command-line options are preserved, allowing plugins better control
of the help displayed to users.
#6940: When using the
--durationoption, the terminal message output is now more precise about the number and duration of hidden items.#6991: Collected files are displayed after any reports from hooks, e.g. the status from
--lf.#7091: When
fdcapturing is used, through--capture=fdor thecapfdandcapfdbinaryfixtures, and the file descriptor (0, 1, 2) cannot beduplicated, FD capturing is still performed. Previously, direct writes to the
file descriptors would fail or be lost in this case.
#7119: Exit with an error if the
--basetempargument is empty, is the current working directory or is one of the parent directories.This is done to protect against accidental data loss, as any directory passed to this argument is cleared.
#7128: pytest --version now displays just the pytest version, while pytest --version --version displays more verbose information including plugins. This is more consistent with how other tools show --version.
#7133: caplog.set_level() <_pytest.logging.LogCaptureFixture.set_level> will now override any log_level set via the CLI or configuration file.
#7159: caplog.set_level() <_pytest.logging.LogCaptureFixture.set_level> and caplog.at_level() <_pytest.logging.LogCaptureFixture.at_level> no longer affect
the level of logs that are shown in the Captured log report report section.
#7348: Improve recursive diff report for comparison asserts on dataclasses / attrs.
#7385:
--junitxmlnow includes the exception cause in themessageXML attribute for failures during setup and teardown.Previously:
Now:
Bug Fixes
#1120: Fix issue where directories from tmpdir are not removed properly when multiple instances of pytest are running in parallel.
#4583: Prevent crashing and provide a user-friendly error when a marker expression (-m) invoking of eval raises any exception.
#4677: The path shown in the summary report for SKIPPED tests is now always relative. Previously it was sometimes absolute.
#5456: Fix a possible race condition when trying to remove lock files used to control access to folders
created by tmp_path and tmpdir.
#6240: Fixes an issue where logging during collection step caused duplication of log
messages to stderr.
#6428: Paths appearing in error messages are now correct in case the current working directory has
changed since the start of the session.
#6755: Support deleting paths longer than 260 characters on windows created inside tmpdir.
#6871: Fix crash with captured output when using capsysbinary.
#6909: Revert the change introduced by #6330, which required all arguments to
@pytest.mark.parametrizeto be explicitly defined in the function signature.The intention of the original change was to remove what was expected to be an unintended/surprising behavior, but it turns out many people relied on it, so the restriction has been reverted.
#6910: Fix crash when plugins return an unknown stats while using the
--reportlogoption.#6924: Ensure a
unittest.IsolatedAsyncioTestCaseis actually awaited.#6925: Fix TerminalRepr instances to be hashable again.
#6947: Fix regression where functions registered with unittest.TestCase.addCleanup were not being called on test failures.
#6951: Allow users to still set the deprecated
TerminalReporter.writerattribute.#6956: Prevent pytest from printing ConftestImportFailure traceback to stdout.
#6991: Fix regressions with --lf filtering too much since pytest 5.4.
#6992: Revert "tmpdir: clean up indirection via config for factories" #6767 as it breaks pytest-xdist.
#7061: When a yielding fixture fails to yield a value, report a test setup error instead of crashing.
#7076: The path of file skipped by
@pytest.mark.skipin the SKIPPED report is now relative to invocation directory. Previously it was relative to root directory.#7110: Fixed regression:
asyncbase.TestCasetests are executed correctly again.#7126:
--setup-shownow doesn't raise an error when a bytes value is used as aparametrizeparameter when Python is called with the
-bbflag.#7143: Fix pytest.File.from_parent so it forwards extra keyword arguments to the constructor.
#7145: Classes with broken
__getattribute__methods are displayed correctly during failures.#7150: Prevent hiding the underlying exception when
ConfTestImportFailureis raised.#7180: Fix
_is_setup_pyfor files encoded differently than locale.#7215: Fix regression where running with
--pdbwould call unittest.TestCase.tearDown for skipped tests.#7253: When using
pytest.fixtureon a function directly, as inpytest.fixture(func),if the
autouseorparamsarguments are also passed, the function is no longerignored, but is marked as a fixture.
#7360: Fix possibly incorrect evaluation of string expressions passed to
pytest.mark.skipifandpytest.mark.xfail,in rare circumstances where the exact same string is used but refers to different global values.
#7383: Fixed exception causes all over the codebase, i.e. use raise new_exception from old_exception when wrapping an exception.
Improved Documentation
--strictand--strict-markersand the preference for the latter one.Trivial/Internal Changes
originalnameattribute of_pytest.python.Functionnow defaults tonameif notprovided explicitly, and is always set.
wcwidthpackage has been removed.py.iniconfigwith iniconfig.src/_pytest/config/__init__.pynow uses thewarningsmodule to report warnings instead ofsys.stderr.write.pytest-xdist.py>=1.8.2 is now required.v5.4.3Compare Source
pytest 5.4.3 (2020-06-02)
Bug Fixes
changed since the start of the session.
ConfTestImportFailureis raised.--pdbwould call thetearDownmethods ofunittest.TestCasesubclasses for skipped tests.
v5.4.2Compare Source
pytest 5.4.2 (2020-05-08)
Bug Fixes
unittest.IsolatedAsyncioTestCaseis actually awaited.TestCase.addCleanupwere not being called on test failures.TerminalReporter.writerattribute.asyncbase.TestCasetests are executed correctly again.File.from_constructorso it forwards extra keyword arguments to the constructor.__getattribute__methods are displayed correctly during failures._is_setup_pyfor files encoded differently than locale.v5.4.1Compare Source
pytest 5.4.1 (2020-03-13)
Bug Fixes
#6909: Revert the change introduced by #6330, which required all arguments to
@pytest.mark.parametrizeto be explicitly defined in the function signature.The intention of the original change was to remove what was expected to be an unintended/surprising behavior, but it turns out many people relied on it, so the restriction has been reverted.
#6910: Fix crash when plugins return an unknown stats while using the
--reportlogoption.v5.4.0Compare Source
Breaking Changes
#6316: Matching of
-k EXPRESSIONto test names is now case-insensitive.#6443: Plugins specified with
-pare now loaded after internal plugins, which results in their hooks being called before the internal ones.This makes the
-pbehavior consistent withPYTEST_PLUGINS.#6637: Removed the long-deprecated
pytest_itemstarthook.This hook has been marked as deprecated and not been even called by pytest for over 10 years now.
#6673: Reversed / fix meaning of \"+/-\" in error diffs. \"-\" means that sth. expected is missing in the result and \"+\" means that there are unexpected extras in the result.
#6737: The
cached_resultattribute ofFixtureDefis now set toNonewhenthe result is unavailable, instead of being deleted.
If your plugin performs checks like
hasattr(fixturedef, 'cached_result'),for example in a
pytest_fixture_post_finalizerhook implementation, replaceit with
fixturedef.cached_result is not None. If youdelthe attribute,set it to
Noneinstead.Deprecations
#3238: Option
--no-print-logsis deprecated and meant to be removed in a future release. If you use--no-print-logs, please try out--show-captureandprovide feedback.
--show-capturecommand-line option was added inpytest 3.5.0and allows to specify how todisplay captured output when tests fail:
no,stdout,stderr,logorall(the default).#571: Deprecate the unused/broken [pytest_collect_directory]{.title-ref} hook.
It was misaligned since the removal of the
Directorycollector in 2010and incorrect/unusable as soon as collection was split from test execution.
#5975: Deprecate using direct constructors for
Nodes.Instead they are new constructed via
Node.from_parent.This transitional mechanism enables us to detangle the very intensely
entangled
Noderelationships by enforcing more controlled creation/configruation patterns.As part of that session/config are already disallowed parameters and as we work on the details we might need disallow a few more as well.
Subclasses are expected to use [super().from_parent]{.title-ref} if they intend to expand the creation of [Nodes]{.title-ref}.
#6779: The
TerminalReporter.writerattribute has been deprecated and should no longer be used. Thiswas inadvertently exposed as part of the public API of that plugin and ties it too much
with
py.io.TerminalWriter.Features
--capture=tee-sys <capture-method>{.interpreted-text role="ref"} option to allow both live printing and capturing of test output.@pytest.mark.parametrizeneed to be explicitly declared in the function signature or viaindirect.Previously it was possible to omit an argument if a fixture with the same name existed, which was just an accident of implementation and was not meant to be a part of the API.
short test summary <pytest.detailed_failed_tests_usage>{.interpreted-text role="ref"}. [-rN]{.title-ref} can be used to disable it (the old behavior).junit_logging{.interpreted-text role="confval"} option:log,out-err, andall.Improvements
#1857:
pytest.mark.parametrizeaccepts integers foridsagain, converting it to strings.#449: Use \"yellow\" main color with any XPASSED tests.
#4639: Revert \"A warning is now issued when assertions are made for
None\".The warning proved to be less useful than initially expected and had quite a
few false positive cases.
#5686:
tmpdir_factory.mktempnow fails when given absolute and non-normalized paths.#5984: The
pytest_warning_capturedhook now receives alocationparameter with the code location that generated the warning.#6213: pytester: the
testdirfixture respects environment settings from themonkeypatchfixture for inner runs.#6247:
--fulltraceis honored with collection errors.#6384: Make [--showlocals]{.title-ref} work also with [--tb=short]{.title-ref}.
#6653: Add support for matching lines consecutively with
LineMatcher <_pytest.pytester.LineMatcher>{.interpreted-text role="attr"}\'s~_pytest.pytester.LineMatcher.fnmatch_lines{.interpreted-text role="func"} and~_pytest.pytester.LineMatcher.re_match_lines{.interpreted-text role="func"}.#6658: Code is now highlighted in tracebacks when
pygmentsis installed.Users are encouraged to install
pygmentsinto their environment and provide feedback, becausethe plan is to make
pygmentsa regular dependency in the future.#6795: Import usage error message with invalid [-o]{.title-ref} option.
#759:
pytest.mark.parametrizesupports iterators and generators forids.Bug Fixes
#310: Add support for calling [pytest.xfail()]{.title-ref} and [pytest.importorskip()]{.title-ref} with doctests.
#3823:
--tracenow works with unittests.#4445: Fixed some warning reports produced by pytest to point to the correct location of the warning in the user\'s code.
#5301: Fix
--last-failedto collect new tests from files with known failures.#5928: Report
PytestUnknownMarkWarningat the level of the user\'s code, notpytest\'s.#5991: Fix interaction with
--pdband unittests: do not use unittest\'sTestCase.debug().#6334: Fix summary entries appearing twice when
f/Fands/Sreport chars were used at the same time in the-rcommand-line option (for example-rFf).The upper case variants were never documented and the preferred form should be the lower case.
#6409: Fallback to green (instead of yellow) for non-last items without previous passes with colored terminal progress indicator.
#6454: [--disable-warnings]{.title-ref} is honored with [-ra]{.title-ref} and [-rA]{.title-ref}.
#6497: Fix bug in the comparison of request key with cached key in fixture.
A construct
if key == cached_key:can fail either because==is explicitly disallowed, or for, e.g., NumPy arrays, where the result ofa == bcannot generally be converted to [bool]{.title-ref}.The implemented fix replaces [==]{.title-ref} with
is.#6557: Make capture output streams
.write()method return the same return value from original streams.#6566: Fix
EncodedFile.writelinesto call the underlying buffer\'swritelinesmethod.#6575: Fix internal crash when
faulthandlerstarts initialized(for example with
PYTHONFAULTHANDLER=1environment variable set) andfaulthandler_timeoutdefinedin the configuration file.
#6597: Fix node ids which contain a parametrized empty-string variable.
#6646: Assertion rewriting hooks are (re)stored for the current item, which fixes them being still used after e.g. pytester\'s
testdir.runpytest <_pytest.pytester.Testdir.runpytest>{.interpreted-text role="func"} etc.#6660:
pytest.exit() <_pytest.outcomes.exit>{.interpreted-text role="func"} is handled when emitted from thepytest_sessionfinish <_pytest.hookspec.pytest_sessionfinish>{.interpreted-text role="func"} hook. This includes quitting from a debugger.#6752: When :py
pytest.raises{.interpreted-text role="func"} is used as a function (as opposed to a context manager),a [match]{.title-ref} keyword argument is now passed through to the tested function. Previously
it was swallowed and ignored (regression in pytest 5.1.0).
#6801: Do not display empty lines inbetween traceback for unexpected exceptions with doctests.
#6802: The
testdir fixture <testdir>{.interpreted-text role="fixture"} works within doctests now.Improved Documentation
Trivial/Internal Changes
parsermodule, deprecated in Python 3.9.v5.3.5Compare Source
pytest 5.3.5 (2020-01-29)
Bug Fixes
regression in pytest 5.3.4 causing an INTERNALERROR due to a wrong
assertion.
v5.3.4Compare Source
pytest 5.3.4 (2020-01-20)
Bug Fixes
#6436:
unfortunately this change has caused a number of regressions in many
suites, so the team decided to revert this change and make a new
release while we continue to look for a solution.
v5.3.3Compare Source
pytest 5.3.3 (2020-01-16)
Bug Fixes
output during teardown is shown with
-rP.pytest-xdistcrash when dealing with exceptions raised insubprocesses created by the
multiprocessingmodule.FixtureDef <_pytest.fixtures.FixtureDef> objects now properly
register their finalizers with autouse and parameterized fixtures
that execute before them in the fixture stack so they are torn down
at the right times, and in the right order.
parsing of outcomes containing multiple errors with
testdirresults (regression in 5.3.0).
Trivial/Internal Changes
Optimized automatic renaming of test parameter IDs.
Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Never, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by WhiteSource Renovate. View repository job log here.