Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bump pytest from 4.4.2 to 4.5.0 #45

Merged
merged 1 commit into from
May 13, 2019
Merged

Bump pytest from 4.4.2 to 4.5.0 #45

merged 1 commit into from
May 13, 2019

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps pytest from 4.4.2 to 4.5.0.

Changelog

Sourced from pytest's changelog.

pytest 4.5.0 (2019-05-11)

Features

  • #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: Show XFail reason as part of JUnitXML message field.

  • #5013: Messages from crash reports are displayed within test summaries now, truncated to the terminal width.

  • #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: Assertion failure messages for sequences and dicts contain the number of different items now.

  • #5034: Improve reporting with --lf and --ff (run-last-failure).

  • #5035: The --cache-show option/action accepts an optional glob to show only matching cache entries.

  • #5059: Standard input (stdin) can be given to pytester's Testdir.run() and Testdir.popen().

  • #5068: The -r option learnt about A to display all reports (including passed ones) in the short test summary.

  • #5108: The short test summary is displayed after passes with output (-rP).

  • #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: 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: New record_testsuite_property session-scoped fixture allows users to log <property> 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: 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 configuration option.

  • #5220: --fixtures now also shows fixture scope for scopes other than "function".

Bug Fixes

  • #5113: Deselected items from plugins using pytest_collect_modifyitems as a hookwrapper are correctly reported now.
  • #5144: With usage errors exitstatus is set to EXIT_USAGEERROR in the pytest_sessionfinish hook now as expected.
  • #5235: outcome.exit is not used with EOF in the pdb wrapper anymore, but only with quit.
... (truncated)
Commits
  • 63fe547 Preparing release version 4.5.0
  • b709e61 Merge remote-tracking branch 'upstream/master' into release-4.5.0
  • 465b2d9 Further "unknown marks warning" improvements (#5178)
  • 184ef92 Introduce record_testsuite_property fixture (#5205)
  • 73bbff2 Introduce record_testsuite_property fixture
  • 4ccaa98 Merge pull request #5240 from nicoddemus/tidelift
  • 3a4a815 Merge master into features (#5233)
  • dae455e Add Tidelift management docs and blurb on README, as discussed in the ML
  • 0594dba Remove unused markers and enable --strict-markers
  • f1183c2 Remove the 'issue' marker from test suite
  • Additional commits viewable in compare view

Dependabot compatibility score

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.

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:

  • 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.

@dependabot-support
Bump pytest from 4.4.2 to 4.5.0
a3be80b 
Bumps [pytest](https://github.com/pytest-dev/pytest) from 4.4.2 to 4.5.0.
- [Release notes](https://github.com/pytest-dev/pytest/releases)
- [Changelog](https://github.com/pytest-dev/pytest/blob/master/CHANGELOG.rst)
- [Commits](pytest-dev/pytest@4.4.2...4.5.0)

Signed-off-by: dependabot[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label May 13, 2019
@coveralls
Copy link

coveralls commented May 13, 2019 •
edited

Pull Request Test Coverage Report for Build 131

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 100.0%
Totals Coverage Status
Change from base Build 129: 0.0%
Covered Lines: 13
Relevant Lines: 13
💛 - Coveralls

@sobolevn sobolevn merged commit 572289a into master May 13, 2019
@dependabot-preview dependabot-preview bot deleted the dependabot/pip/pytest-4.5.0 branch May 13, 2019 12:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@coveralls @sobolevn @dependabot-support