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.

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

MAINT: Bump pytest from 5.2.4 to 5.3.0 #14978

Merged
merged 1 commit into from
Nov 25, 2019
Merged

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps pytest from 5.2.4 to 5.3.0.

Release notes

Sourced from pytest's releases.

5.3.0

pytest 5.3.0 (2019-11-19)

Deprecations

  • #6179: The
    default value of junit_family option will change to xunit2 in
    pytest 6.0, given that this is the version supported by default in
    modern tools that manipulate this type of file.

    In order to smooth the transition, pytest will issue a warning in
    case the --junitxml option is given in the command line but
    junit_family is not explicitly configured in pytest.ini.

    For more information, see the
    docs
    .

Features

  • #4488: The
    pytest team has created the
    pytest-reportlog
    plugin, which provides a new --report-log=FILE option that writes
    report logs into a file as the test session executes.

    Each line of the report log contains a self contained JSON object
    corresponding to a testing event, such as a collection or a test
    result report. The file is guaranteed to be flushed after writing
    each line, so systems can read and process events in real-time.

    The plugin is meant to replace the --resultlog option, which is
    deprecated and meant to be removed in a future release. If you use
    --resultlog, please try out pytest-reportlog and
    provide feedback.

  • #4730: When
    sys.pycache_prefix (Python 3.8+) is set, it will be used by pytest
    to cache test files changed by the assertion rewriting mechanism.

    This makes it easier to benefit of cached .pyc files even on file
    systems without permissions.

  • #5515: Allow
    selective auto-indentation of multiline log messages.

    Adds command line option --log-auto-indent, config option
    log_auto_indent and support for per-entry configuration of

... (truncated)
Changelog

Sourced from pytest's changelog.

pytest 5.3.0 (2019-11-19)

Deprecations

  • #6179: The default value of junit_family option will change to xunit2 in pytest 6.0, given that this is the version supported by default in modern tools that manipulate this type of file.

    In order to smooth the transition, pytest will issue a warning in case the --junitxml option is given in the command line but junit_family is not explicitly configured in pytest.ini.

    For more information, see the docs.

Features

  • #4488: The pytest team has created the pytest-reportlog plugin, which provides a new --report-log=FILE option that writes report logs into a file as the test session executes.

    Each line of the report log contains a self contained JSON object corresponding to a testing event, such as a collection or a test result report. The file is guaranteed to be flushed after writing each line, so systems can read and process events in real-time.

    The plugin is meant to replace the --resultlog option, which is deprecated and meant to be removed in a future release. If you use --resultlog, please try out pytest-reportlog and provide feedback.

  • #4730: When sys.pycache_prefix (Python 3.8+) is set, it will be used by pytest to cache test files changed by the assertion rewriting mechanism.

    This makes it easier to benefit of cached .pyc files even on file systems without permissions.

  • #5515: Allow selective auto-indentation of multiline log messages.

    Adds command line option --log-auto-indent, config option log_auto_indent and support for per-entry configuration of indentation behavior on calls to logging.log().

    Alters the default for auto-indention from on to off. This restores the older behavior that existed prior to v4.6.0. This reversion to earlier behavior was done because it is better to activate new features that may lead to broken tests explicitly rather than implicitly.

  • #5914: testdir learned two new functions, no_fnmatch_line and no_re_match_line.

    The functions are used to ensure the captured text does not match the given pattern.

    The previous idiom was to use re.match:

    result = testdir.runpytest()
    assert re.match(pat, result.stdout.str()) is None
    

    Or the in operator:

    result = testdir.runpytest()
    assert text in result.stdout.str()
    

    But the new functions produce best output on failure.

... (truncated)
Commits
  • be59827 Small fixes in the CHANGELOG for 5.3.0
  • 4b16b93 Preparing release version 5.3.0
  • 21622d0 Merge remote-tracking branch 'upstream/master' into release-5.3.0
  • d1e2d12 python: remove unused pytest_make_parametrize_id hookimpl (#6228)
  • f36ea24 Remove check for os.symlink, always there in py3+ (#6227)
  • 4804d4b python: remove unused pytest_make_parametrize_id hookimpl
  • b820b7e Merge pull request #6224 from blueyed/visit_Assert-minor-cleanup
  • 8d3e8b1 Revert "ci: use tox -vv" (#6226)
  • 63a23d8 Remove check for os.symlink, always there in py3+
  • eeeb196 Merge pull request #6202 from linw1995/fix_getmodpath
  • 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 close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor 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 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 the .dependabot/config.yml file in this repo:

  • Update frequency
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Bumps [pytest](https://github.com/pytest-dev/pytest) from 5.2.4 to 5.3.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@5.2.4...5.3.0)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@seberg seberg merged commit 9ed9806 into master Nov 25, 2019
@dependabot-preview dependabot-preview bot deleted the dependabot/pip/pytest-5.3.0 branch November 25, 2019 16:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant