Updates the requirements on pytest to permit the latest version.
Changelog
*Sourced from [pytest's changelog](https://github.com/pytest-dev/pytest/blob/master/CHANGELOG.rst).*
> pytest 4.5.0 (2019-05-11)
> =========================
>
> Features
> --------
>
> - [\#4826](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/4826): A warning is now emitted when unknown marks are used as a decorator. This is often due to a typo, which can lead to silently broken tests.
> - [\#4907](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/4907): Show XFail reason as part of JUnitXML message field.
> - [\#5013](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5013): Messages from crash reports are displayed within test summaries now, truncated to the terminal width.
> - [\#5023](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5023): New flag `--strict-markers` that triggers an error when unknown markers (e.g. those not registered using the [markers option]() in the configuration file) are used in the test suite.
>
> The existing `--strict` option has the same behavior currently, but can be augmented in the future for additional checks.
>
> - [\#5026](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5026): Assertion failure messages for sequences and dicts contain the number of different items now.
> - [\#5034](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5034): Improve reporting with `--lf` and `--ff` (run-last-failure).
> - [\#5035](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5035): The `--cache-show` option/action accepts an optional glob to show only matching cache entries.
> - [\#5059](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5059): Standard input (stdin) can be given to pytester's `Testdir.run()` and `Testdir.popen()`.
> - [\#5068](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5068): The `-r` option learnt about `A` to display all reports (including passed ones) in the short test summary.
> - [\#5108](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5108): The short test summary is displayed after passes with output (`-rP`).
> - [\#5172](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5172): The `--last-failed` (`--lf`) option got smarter and will now skip entire files if all tests of that test file have passed in previous runs, greatly speeding up collection.
> - [\#5177](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5177): Introduce new specific warning `PytestWarning` subclasses to make it easier to filter warnings based on the class, rather than on the message. The new subclasses are:
> - `PytestAssertRewriteWarning`
> - `PytestCacheWarning`
> - `PytestCollectionWarning`
> - `PytestConfigWarning`
> - `PytestUnhandledCoroutineWarning`
> - `PytestUnknownMarkWarning`
> - [\#5202](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5202): New `record_testsuite_property` session-scoped fixture allows users to log `` tags at the `testsuite` level with the `junitxml` plugin.
>
> The generated XML is compatible with the latest xunit standard, contrary to the properties recorded by `record_property` and `record_xml_attribute`.
>
> - [\#5214](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5214): The default logging format has been changed to improve readability. Here is an example of a previous logging message:
>
> test_log_cli_enabled_disabled.py 3 CRITICAL critical message logged by test
>
> This has now become:
>
> CRITICAL root:test_log_cli_enabled_disabled.py:3 critical message logged by test
>
> The formatting can be changed through the [log\_format](https://docs.pytest.org/en/latest/reference.html#confval-log_format) configuration option.
>
> - [\#5220](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5220): `--fixtures` now also shows fixture scope for scopes other than `"function"`.
>
> Bug Fixes
> ---------
>
> - [\#5113](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5113): Deselected items from plugins using `pytest_collect_modifyitems` as a hookwrapper are correctly reported now.
> - [\#5144](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5144): With usage errors `exitstatus` is set to `EXIT_USAGEERROR` in the `pytest_sessionfinish` hook now as expected.
> - [\#5235](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5235): `outcome.exit` is not used with `EOF` in the pdb wrapper anymore, but only with `quit`.
>
> ... (truncated)
Commits
- [`63fe547`](https://github.com/pytest-dev/pytest/commit/63fe547d9f97a78c63a91e139d3a17c15afe7e84) Preparing release version 4.5.0
- [`b709e61`](https://github.com/pytest-dev/pytest/commit/b709e618923c138e5d4031a7f1dc12716c488e65) Merge remote-tracking branch 'upstream/master' into release-4.5.0
- [`465b2d9`](https://github.com/pytest-dev/pytest/commit/465b2d998ab6d05a99c84687a1ee0128131a79fd) Further "unknown marks warning" improvements ([#5178](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5178))
- [`184ef92`](https://github.com/pytest-dev/pytest/commit/184ef92f0b22fa79ae2d270f36549cbe0804a882) Introduce record_testsuite_property fixture ([#5205](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5205))
- [`73bbff2`](https://github.com/pytest-dev/pytest/commit/73bbff2b7459e2523973ac90dcbf15c3b4e1684a) Introduce record_testsuite_property fixture
- [`4ccaa98`](https://github.com/pytest-dev/pytest/commit/4ccaa987d47566e3907f2f74167c4ab7997f622f) Merge pull request [#5240](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5240) from nicoddemus/tidelift
- [`3a4a815`](https://github.com/pytest-dev/pytest/commit/3a4a815c41badd1a6bac958aa18ddeb0c16cd202) Merge master into features ([#5233](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5233))
- [`dae455e`](https://github.com/pytest-dev/pytest/commit/dae455e8a32810aa3035ac3c5f2f802a06b851d3) Add Tidelift management docs and blurb on README, as discussed in the ML
- [`0594dba`](https://github.com/pytest-dev/pytest/commit/0594dba5ce76628902dfd3ee107c6c2d10c7d73a) Remove unused markers and enable --strict-markers
- [`f1183c2`](https://github.com/pytest-dev/pytest/commit/f1183c242275eafd5ad5e594bd631f694c18833a) Remove the 'issue' marker from test suite
- Additional commits viewable in [compare view](https://github.com/pytest-dev/pytest/compare/3.5.0...4.5.0)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.
You can always request more updates by clicking Bump now in your Dependabot dashboard.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Finally, you can contact us by mentioning @dependabot.
Updates the requirements on pytest to permit the latest version.
Changelog
*Sourced from [pytest's changelog](https://github.com/pytest-dev/pytest/blob/master/CHANGELOG.rst).* > pytest 4.5.0 (2019-05-11) > ========================= > > Features > -------- > > - [\#4826](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/4826): A warning is now emitted when unknown marks are used as a decorator. This is often due to a typo, which can lead to silently broken tests. > - [\#4907](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/4907): Show XFail reason as part of JUnitXML message field. > - [\#5013](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5013): Messages from crash reports are displayed within test summaries now, truncated to the terminal width. > - [\#5023](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5023): New flag `--strict-markers` that triggers an error when unknown markers (e.g. those not registered using the [markers option]() in the configuration file) are used in the test suite. > > The existing `--strict` option has the same behavior currently, but can be augmented in the future for additional checks. > > - [\#5026](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5026): Assertion failure messages for sequences and dicts contain the number of different items now. > - [\#5034](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5034): Improve reporting with `--lf` and `--ff` (run-last-failure). > - [\#5035](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5035): The `--cache-show` option/action accepts an optional glob to show only matching cache entries. > - [\#5059](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5059): Standard input (stdin) can be given to pytester's `Testdir.run()` and `Testdir.popen()`. > - [\#5068](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5068): The `-r` option learnt about `A` to display all reports (including passed ones) in the short test summary. > - [\#5108](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5108): The short test summary is displayed after passes with output (`-rP`). > - [\#5172](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5172): The `--last-failed` (`--lf`) option got smarter and will now skip entire files if all tests of that test file have passed in previous runs, greatly speeding up collection. > - [\#5177](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5177): Introduce new specific warning `PytestWarning` subclasses to make it easier to filter warnings based on the class, rather than on the message. The new subclasses are: > - `PytestAssertRewriteWarning` > - `PytestCacheWarning` > - `PytestCollectionWarning` > - `PytestConfigWarning` > - `PytestUnhandledCoroutineWarning` > - `PytestUnknownMarkWarning` > - [\#5202](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5202): New `record_testsuite_property` session-scoped fixture allows users to log `Commits
- [`63fe547`](https://github.com/pytest-dev/pytest/commit/63fe547d9f97a78c63a91e139d3a17c15afe7e84) Preparing release version 4.5.0 - [`b709e61`](https://github.com/pytest-dev/pytest/commit/b709e618923c138e5d4031a7f1dc12716c488e65) Merge remote-tracking branch 'upstream/master' into release-4.5.0 - [`465b2d9`](https://github.com/pytest-dev/pytest/commit/465b2d998ab6d05a99c84687a1ee0128131a79fd) Further "unknown marks warning" improvements ([#5178](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5178)) - [`184ef92`](https://github.com/pytest-dev/pytest/commit/184ef92f0b22fa79ae2d270f36549cbe0804a882) Introduce record_testsuite_property fixture ([#5205](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5205)) - [`73bbff2`](https://github.com/pytest-dev/pytest/commit/73bbff2b7459e2523973ac90dcbf15c3b4e1684a) Introduce record_testsuite_property fixture - [`4ccaa98`](https://github.com/pytest-dev/pytest/commit/4ccaa987d47566e3907f2f74167c4ab7997f622f) Merge pull request [#5240](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5240) from nicoddemus/tidelift - [`3a4a815`](https://github.com/pytest-dev/pytest/commit/3a4a815c41badd1a6bac958aa18ddeb0c16cd202) Merge master into features ([#5233](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5233)) - [`dae455e`](https://github.com/pytest-dev/pytest/commit/dae455e8a32810aa3035ac3c5f2f802a06b851d3) Add Tidelift management docs and blurb on README, as discussed in the ML - [`0594dba`](https://github.com/pytest-dev/pytest/commit/0594dba5ce76628902dfd3ee107c6c2d10c7d73a) Remove unused markers and enable --strict-markers - [`f1183c2`](https://github.com/pytest-dev/pytest/commit/f1183c242275eafd5ad5e594bd631f694c18833a) Remove the 'issue' marker from test suite - Additional commits viewable in [compare view](https://github.com/pytest-dev/pytest/compare/3.5.0...4.5.0)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.
You can always request more updates by clicking
Bump nowin your Dependabot dashboard.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot.