Compare commits
1 Commits
main
...
fix/ellips
| Author | SHA1 | Date |
|---|---|---|
Sorin Sbarnea
|
66a18f7199 |
|
|
@ -29,5 +29,3 @@ exclude_lines =
|
||||||
|
|
||||||
^\s*if TYPE_CHECKING:
|
^\s*if TYPE_CHECKING:
|
||||||
^\s*@overload( |$)
|
^\s*@overload( |$)
|
||||||
|
|
||||||
^\s*@pytest\.mark\.xfail
|
|
||||||
|
|
|
||||||
|
|
@ -1,20 +0,0 @@
|
||||||
---
|
|
||||||
|
|
||||||
branch-protection-check-name: Changelog entry
|
|
||||||
action-hints:
|
|
||||||
check-title-prefix: "Chronographer: "
|
|
||||||
external-docs-url: >-
|
|
||||||
https://docs.pytest.org/en/latest/contributing.html#preparing-pull-requests
|
|
||||||
inline-markdown: >-
|
|
||||||
See
|
|
||||||
https://docs.pytest.org/en/latest/contributing.html#preparing-pull-requests
|
|
||||||
for details.
|
|
||||||
enforce-name:
|
|
||||||
suffix: .rst
|
|
||||||
exclude:
|
|
||||||
humans:
|
|
||||||
- pyup-bot
|
|
||||||
labels:
|
|
||||||
skip-changelog: skip news
|
|
||||||
|
|
||||||
...
|
|
||||||
|
|
@ -1,7 +0,0 @@
|
||||||
---
|
|
||||||
|
|
||||||
backport_branch_prefix: patchback/backports/
|
|
||||||
backport_label_prefix: 'backport ' # IMPORTANT: the labels are space-delimited
|
|
||||||
# target_branch_prefix: '' # The project's backport branches are non-prefixed
|
|
||||||
|
|
||||||
...
|
|
||||||
|
|
@ -0,0 +1,51 @@
|
||||||
|
name: backport
|
||||||
|
|
||||||
|
on:
|
||||||
|
# Note that `pull_request_target` has security implications:
|
||||||
|
# https://securitylab.github.com/research/github-actions-preventing-pwn-requests/
|
||||||
|
# In particular:
|
||||||
|
# - Only allow triggers that can be used only be trusted users
|
||||||
|
# - Don't execute any code from the target branch
|
||||||
|
# - Don't use cache
|
||||||
|
pull_request_target:
|
||||||
|
types: [labeled]
|
||||||
|
|
||||||
|
# Set permissions at the job level.
|
||||||
|
permissions: {}
|
||||||
|
|
||||||
|
jobs:
|
||||||
|
backport:
|
||||||
|
if: startsWith(github.event.label.name, 'backport ') && github.event.pull_request.merged
|
||||||
|
runs-on: ubuntu-latest
|
||||||
|
permissions:
|
||||||
|
contents: write
|
||||||
|
pull-requests: write
|
||||||
|
|
||||||
|
steps:
|
||||||
|
- uses: actions/checkout@v4
|
||||||
|
with:
|
||||||
|
fetch-depth: 0
|
||||||
|
persist-credentials: true
|
||||||
|
|
||||||
|
- name: Create backport PR
|
||||||
|
run: |
|
||||||
|
set -eux
|
||||||
|
|
||||||
|
git config --global user.name "pytest bot"
|
||||||
|
git config --global user.email "pytestbot@gmail.com"
|
||||||
|
|
||||||
|
label='${{ github.event.label.name }}'
|
||||||
|
target_branch="${label#backport }"
|
||||||
|
backport_branch=backport-${{ github.event.number }}-to-"${target_branch}"
|
||||||
|
subject="[$target_branch] $(gh pr view --json title -q .title ${{ github.event.number }})"
|
||||||
|
|
||||||
|
git checkout origin/"${target_branch}" -b "${backport_branch}"
|
||||||
|
git cherry-pick -x --mainline 1 ${{ github.event.pull_request.merge_commit_sha }}
|
||||||
|
git commit --amend --message "$subject"
|
||||||
|
git push --set-upstream origin --force-with-lease "${backport_branch}"
|
||||||
|
gh pr create \
|
||||||
|
--base "${target_branch}" \
|
||||||
|
--title "${subject}" \
|
||||||
|
--body "Backport of PR #${{ github.event.number }} to $target_branch branch. PR created by backport workflow."
|
||||||
|
env:
|
||||||
|
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
||||||
|
|
@ -19,11 +19,6 @@ jobs:
|
||||||
SETUPTOOLS_SCM_PRETEND_VERSION: ${{ github.event.inputs.version }}
|
SETUPTOOLS_SCM_PRETEND_VERSION: ${{ github.event.inputs.version }}
|
||||||
timeout-minutes: 10
|
timeout-minutes: 10
|
||||||
|
|
||||||
# Required by attest-build-provenance-github.
|
|
||||||
permissions:
|
|
||||||
id-token: write
|
|
||||||
attestations: write
|
|
||||||
|
|
||||||
steps:
|
steps:
|
||||||
- uses: actions/checkout@v4
|
- uses: actions/checkout@v4
|
||||||
with:
|
with:
|
||||||
|
|
@ -31,9 +26,7 @@ jobs:
|
||||||
persist-credentials: false
|
persist-credentials: false
|
||||||
|
|
||||||
- name: Build and Check Package
|
- name: Build and Check Package
|
||||||
uses: hynek/build-and-inspect-python-package@v2.6.0
|
uses: hynek/build-and-inspect-python-package@v2.4.0
|
||||||
with:
|
|
||||||
attest-build-provenance-github: 'true'
|
|
||||||
|
|
||||||
deploy:
|
deploy:
|
||||||
if: github.repository == 'pytest-dev/pytest'
|
if: github.repository == 'pytest-dev/pytest'
|
||||||
|
|
@ -54,7 +47,7 @@ jobs:
|
||||||
path: dist
|
path: dist
|
||||||
|
|
||||||
- name: Publish package to PyPI
|
- name: Publish package to PyPI
|
||||||
uses: pypa/gh-action-pypi-publish@v1.9.0
|
uses: pypa/gh-action-pypi-publish@v1.8.14
|
||||||
|
|
||||||
- name: Push tag
|
- name: Push tag
|
||||||
run: |
|
run: |
|
||||||
|
|
|
||||||
|
|
@ -14,11 +14,6 @@ on:
|
||||||
branches:
|
branches:
|
||||||
- main
|
- main
|
||||||
- "[0-9]+.[0-9]+.x"
|
- "[0-9]+.[0-9]+.x"
|
||||||
types:
|
|
||||||
- opened # default
|
|
||||||
- synchronize # default
|
|
||||||
- reopened # default
|
|
||||||
- ready_for_review # used in PRs created from the release workflow
|
|
||||||
|
|
||||||
env:
|
env:
|
||||||
PYTEST_ADDOPTS: "--color=yes"
|
PYTEST_ADDOPTS: "--color=yes"
|
||||||
|
|
@ -40,7 +35,7 @@ jobs:
|
||||||
fetch-depth: 0
|
fetch-depth: 0
|
||||||
persist-credentials: false
|
persist-credentials: false
|
||||||
- name: Build and Check Package
|
- name: Build and Check Package
|
||||||
uses: hynek/build-and-inspect-python-package@v2.6.0
|
uses: hynek/build-and-inspect-python-package@v2.4.0
|
||||||
|
|
||||||
build:
|
build:
|
||||||
needs: [package]
|
needs: [package]
|
||||||
|
|
@ -60,7 +55,6 @@ jobs:
|
||||||
"windows-py310",
|
"windows-py310",
|
||||||
"windows-py311",
|
"windows-py311",
|
||||||
"windows-py312",
|
"windows-py312",
|
||||||
"windows-py313",
|
|
||||||
|
|
||||||
"ubuntu-py38",
|
"ubuntu-py38",
|
||||||
"ubuntu-py38-pluggy",
|
"ubuntu-py38-pluggy",
|
||||||
|
|
@ -69,14 +63,12 @@ jobs:
|
||||||
"ubuntu-py310",
|
"ubuntu-py310",
|
||||||
"ubuntu-py311",
|
"ubuntu-py311",
|
||||||
"ubuntu-py312",
|
"ubuntu-py312",
|
||||||
"ubuntu-py313",
|
|
||||||
"ubuntu-pypy3",
|
"ubuntu-pypy3",
|
||||||
|
|
||||||
"macos-py38",
|
"macos-py38",
|
||||||
"macos-py39",
|
"macos-py39",
|
||||||
"macos-py310",
|
"macos-py310",
|
||||||
"macos-py312",
|
"macos-py312",
|
||||||
"macos-py313",
|
|
||||||
|
|
||||||
"doctesting",
|
"doctesting",
|
||||||
"plugins",
|
"plugins",
|
||||||
|
|
@ -105,13 +97,9 @@ jobs:
|
||||||
os: windows-latest
|
os: windows-latest
|
||||||
tox_env: "py311"
|
tox_env: "py311"
|
||||||
- name: "windows-py312"
|
- name: "windows-py312"
|
||||||
python: "3.12"
|
python: "3.12-dev"
|
||||||
os: windows-latest
|
os: windows-latest
|
||||||
tox_env: "py312"
|
tox_env: "py312"
|
||||||
- name: "windows-py313"
|
|
||||||
python: "3.13-dev"
|
|
||||||
os: windows-latest
|
|
||||||
tox_env: "py313"
|
|
||||||
|
|
||||||
- name: "ubuntu-py38"
|
- name: "ubuntu-py38"
|
||||||
python: "3.8"
|
python: "3.8"
|
||||||
|
|
@ -140,15 +128,10 @@ jobs:
|
||||||
tox_env: "py311"
|
tox_env: "py311"
|
||||||
use_coverage: true
|
use_coverage: true
|
||||||
- name: "ubuntu-py312"
|
- name: "ubuntu-py312"
|
||||||
python: "3.12"
|
python: "3.12-dev"
|
||||||
os: ubuntu-latest
|
os: ubuntu-latest
|
||||||
tox_env: "py312"
|
tox_env: "py312"
|
||||||
use_coverage: true
|
use_coverage: true
|
||||||
- name: "ubuntu-py313"
|
|
||||||
python: "3.13-dev"
|
|
||||||
os: ubuntu-latest
|
|
||||||
tox_env: "py313"
|
|
||||||
use_coverage: true
|
|
||||||
- name: "ubuntu-pypy3"
|
- name: "ubuntu-pypy3"
|
||||||
python: "pypy-3.8"
|
python: "pypy-3.8"
|
||||||
os: ubuntu-latest
|
os: ubuntu-latest
|
||||||
|
|
@ -168,13 +151,9 @@ jobs:
|
||||||
os: macos-latest
|
os: macos-latest
|
||||||
tox_env: "py310-xdist"
|
tox_env: "py310-xdist"
|
||||||
- name: "macos-py312"
|
- name: "macos-py312"
|
||||||
python: "3.12"
|
python: "3.12-dev"
|
||||||
os: macos-latest
|
os: macos-latest
|
||||||
tox_env: "py312-xdist"
|
tox_env: "py312-xdist"
|
||||||
- name: "macos-py313"
|
|
||||||
python: "3.13-dev"
|
|
||||||
os: macos-latest
|
|
||||||
tox_env: "py313-xdist"
|
|
||||||
|
|
||||||
- name: "plugins"
|
- name: "plugins"
|
||||||
python: "3.12"
|
python: "3.12"
|
||||||
|
|
@ -187,26 +166,6 @@ jobs:
|
||||||
tox_env: "doctesting"
|
tox_env: "doctesting"
|
||||||
use_coverage: true
|
use_coverage: true
|
||||||
|
|
||||||
continue-on-error: >-
|
|
||||||
${{
|
|
||||||
contains(
|
|
||||||
fromJSON(
|
|
||||||
'[
|
|
||||||
"windows-py38-pluggy",
|
|
||||||
"windows-py313",
|
|
||||||
"ubuntu-py38-pluggy",
|
|
||||||
"ubuntu-py38-freeze",
|
|
||||||
"ubuntu-py313",
|
|
||||||
"macos-py38",
|
|
||||||
"macos-py313"
|
|
||||||
]'
|
|
||||||
),
|
|
||||||
matrix.name
|
|
||||||
)
|
|
||||||
&& true
|
|
||||||
|| false
|
|
||||||
}}
|
|
||||||
|
|
||||||
steps:
|
steps:
|
||||||
- uses: actions/checkout@v4
|
- uses: actions/checkout@v4
|
||||||
with:
|
with:
|
||||||
|
|
@ -247,21 +206,8 @@ jobs:
|
||||||
- name: Upload coverage to Codecov
|
- name: Upload coverage to Codecov
|
||||||
if: "matrix.use_coverage"
|
if: "matrix.use_coverage"
|
||||||
uses: codecov/codecov-action@v4
|
uses: codecov/codecov-action@v4
|
||||||
|
continue-on-error: true
|
||||||
with:
|
with:
|
||||||
fail_ci_if_error: false
|
fail_ci_if_error: true
|
||||||
files: ./coverage.xml
|
files: ./coverage.xml
|
||||||
verbose: true
|
verbose: true
|
||||||
|
|
||||||
check: # This job does nothing and is only used for the branch protection
|
|
||||||
if: always()
|
|
||||||
|
|
||||||
needs:
|
|
||||||
- build
|
|
||||||
|
|
||||||
runs-on: ubuntu-latest
|
|
||||||
|
|
||||||
steps:
|
|
||||||
- name: Decide whether the needed jobs succeeded or failed
|
|
||||||
uses: re-actors/alls-green@223e4bb7a751b91f43eda76992bcfbf23b8b0302
|
|
||||||
with:
|
|
||||||
jobs: ${{ toJSON(needs) }}
|
|
||||||
|
|
|
||||||
|
|
@ -46,8 +46,7 @@ jobs:
|
||||||
run: python scripts/update-plugin-list.py
|
run: python scripts/update-plugin-list.py
|
||||||
|
|
||||||
- name: Create Pull Request
|
- name: Create Pull Request
|
||||||
id: pr
|
uses: peter-evans/create-pull-request@6d6857d36972b65feb161a90e484f2984215f83e
|
||||||
uses: peter-evans/create-pull-request@c5a7806660adbe173f04e3e038b0ccdcd758773c
|
|
||||||
with:
|
with:
|
||||||
commit-message: '[automated] Update plugin list'
|
commit-message: '[automated] Update plugin list'
|
||||||
author: 'pytest bot <pytestbot@users.noreply.github.com>'
|
author: 'pytest bot <pytestbot@users.noreply.github.com>'
|
||||||
|
|
@ -56,13 +55,3 @@ jobs:
|
||||||
branch-suffix: short-commit-hash
|
branch-suffix: short-commit-hash
|
||||||
title: '[automated] Update plugin list'
|
title: '[automated] Update plugin list'
|
||||||
body: '[automated] Update plugin list'
|
body: '[automated] Update plugin list'
|
||||||
draft: true
|
|
||||||
|
|
||||||
- name: Instruct the maintainers to trigger CI by undrafting the PR
|
|
||||||
env:
|
|
||||||
GITHUB_TOKEN: ${{ github.token }}
|
|
||||||
run: >-
|
|
||||||
gh pr comment
|
|
||||||
--body 'Please mark the PR as ready for review to trigger PR checks.'
|
|
||||||
--repo '${{ github.repository }}'
|
|
||||||
'${{ steps.pr.outputs.pull-request-number }}'
|
|
||||||
|
|
|
||||||
|
|
@ -25,6 +25,7 @@ src/_pytest/_version.py
|
||||||
|
|
||||||
doc/*/_build
|
doc/*/_build
|
||||||
doc/*/.doctrees
|
doc/*/.doctrees
|
||||||
|
doc/*/_changelog_towncrier_draft.rst
|
||||||
build/
|
build/
|
||||||
dist/
|
dist/
|
||||||
*.egg-info
|
*.egg-info
|
||||||
|
|
|
||||||
|
|
@ -1,6 +1,6 @@
|
||||||
repos:
|
repos:
|
||||||
- repo: https://github.com/astral-sh/ruff-pre-commit
|
- repo: https://github.com/astral-sh/ruff-pre-commit
|
||||||
rev: "v0.4.10"
|
rev: "v0.4.3"
|
||||||
hooks:
|
hooks:
|
||||||
- id: ruff
|
- id: ruff
|
||||||
args: ["--fix"]
|
args: ["--fix"]
|
||||||
|
|
@ -38,16 +38,11 @@ repos:
|
||||||
# on <3.11
|
# on <3.11
|
||||||
- exceptiongroup>=1.0.0rc8
|
- exceptiongroup>=1.0.0rc8
|
||||||
- repo: https://github.com/tox-dev/pyproject-fmt
|
- repo: https://github.com/tox-dev/pyproject-fmt
|
||||||
rev: "2.1.3"
|
rev: "1.8.0"
|
||||||
hooks:
|
hooks:
|
||||||
- id: pyproject-fmt
|
- id: pyproject-fmt
|
||||||
# https://pyproject-fmt.readthedocs.io/en/latest/#calculating-max-supported-python-version
|
# https://pyproject-fmt.readthedocs.io/en/latest/#calculating-max-supported-python-version
|
||||||
additional_dependencies: ["tox>=4.9"]
|
additional_dependencies: ["tox>=4.9"]
|
||||||
- repo: https://github.com/asottile/pyupgrade
|
|
||||||
rev: v3.16.0
|
|
||||||
hooks:
|
|
||||||
- id: pyupgrade
|
|
||||||
stages: [manual]
|
|
||||||
- repo: local
|
- repo: local
|
||||||
hooks:
|
hooks:
|
||||||
- id: pylint
|
- id: pylint
|
||||||
|
|
@ -66,50 +61,9 @@ repos:
|
||||||
- id: changelogs-rst
|
- id: changelogs-rst
|
||||||
name: changelog filenames
|
name: changelog filenames
|
||||||
language: fail
|
language: fail
|
||||||
entry: >-
|
entry: 'changelog files must be named ####.(breaking|bugfix|deprecation|doc|feature|improvement|trivial|vendor).rst'
|
||||||
changelog files must be named
|
exclude: changelog/(\d+\.(breaking|bugfix|deprecation|doc|feature|improvement|trivial|vendor).rst|README.rst|_template.rst)
|
||||||
####.(
|
|
||||||
breaking
|
|
||||||
| deprecation
|
|
||||||
| feature
|
|
||||||
| improvement
|
|
||||||
| bugfix
|
|
||||||
| vendor
|
|
||||||
| doc
|
|
||||||
| packaging
|
|
||||||
| contrib
|
|
||||||
| misc
|
|
||||||
)(.#)?(.rst)?
|
|
||||||
exclude: >-
|
|
||||||
(?x)
|
|
||||||
^
|
|
||||||
changelog/(
|
|
||||||
\.gitignore
|
|
||||||
|\d+\.(
|
|
||||||
breaking
|
|
||||||
|deprecation
|
|
||||||
|feature
|
|
||||||
|improvement
|
|
||||||
|bugfix
|
|
||||||
|vendor
|
|
||||||
|doc
|
|
||||||
|packaging
|
|
||||||
|contrib
|
|
||||||
|misc
|
|
||||||
)(\.\d+)?(\.rst)?
|
|
||||||
|README\.rst
|
|
||||||
|_template\.rst
|
|
||||||
)
|
|
||||||
$
|
|
||||||
files: ^changelog/
|
files: ^changelog/
|
||||||
- id: changelogs-user-role
|
|
||||||
name: Changelog files should use a non-broken :user:`name` role
|
|
||||||
language: pygrep
|
|
||||||
entry: :user:([^`]+`?|`[^`]+[\s,])
|
|
||||||
pass_filenames: true
|
|
||||||
types:
|
|
||||||
- file
|
|
||||||
- rst
|
|
||||||
- id: py-deprecated
|
- id: py-deprecated
|
||||||
name: py library is deprecated
|
name: py library is deprecated
|
||||||
language: pygrep
|
language: pygrep
|
||||||
|
|
|
||||||
|
|
@ -14,16 +14,11 @@ sphinx:
|
||||||
fail_on_warning: true
|
fail_on_warning: true
|
||||||
|
|
||||||
build:
|
build:
|
||||||
os: ubuntu-24.04
|
os: ubuntu-20.04
|
||||||
tools:
|
tools:
|
||||||
python: >-
|
python: "3.9"
|
||||||
3.12
|
|
||||||
apt_packages:
|
apt_packages:
|
||||||
- inkscape
|
- inkscape
|
||||||
jobs:
|
|
||||||
post_checkout:
|
|
||||||
- git fetch --unshallow || true
|
|
||||||
- git fetch --tags || true
|
|
||||||
|
|
||||||
formats:
|
formats:
|
||||||
- epub
|
- epub
|
||||||
12
AUTHORS
12
AUTHORS
|
|
@ -149,7 +149,6 @@ Evgeny Seliverstov
|
||||||
Fabian Sturm
|
Fabian Sturm
|
||||||
Fabien Zarifian
|
Fabien Zarifian
|
||||||
Fabio Zadrozny
|
Fabio Zadrozny
|
||||||
Farbod Ahmadian
|
|
||||||
faph
|
faph
|
||||||
Felix Hofstätter
|
Felix Hofstätter
|
||||||
Felix Nieuwenhuizen
|
Felix Nieuwenhuizen
|
||||||
|
|
@ -193,7 +192,6 @@ Jake VanderPlas
|
||||||
Jakob van Santen
|
Jakob van Santen
|
||||||
Jakub Mitoraj
|
Jakub Mitoraj
|
||||||
James Bourbeau
|
James Bourbeau
|
||||||
James Frost
|
|
||||||
Jan Balster
|
Jan Balster
|
||||||
Janne Vanhala
|
Janne Vanhala
|
||||||
Jason R. Coombs
|
Jason R. Coombs
|
||||||
|
|
@ -213,7 +211,6 @@ Jordan Guymon
|
||||||
Jordan Moldow
|
Jordan Moldow
|
||||||
Jordan Speicher
|
Jordan Speicher
|
||||||
Joseph Hunkeler
|
Joseph Hunkeler
|
||||||
Joseph Sawaya
|
|
||||||
Josh Karpel
|
Josh Karpel
|
||||||
Joshua Bronson
|
Joshua Bronson
|
||||||
Jurko Gospodnetić
|
Jurko Gospodnetić
|
||||||
|
|
@ -246,7 +243,6 @@ Levon Saldamli
|
||||||
Lewis Cowles
|
Lewis Cowles
|
||||||
Llandy Riveron Del Risco
|
Llandy Riveron Del Risco
|
||||||
Loic Esteve
|
Loic Esteve
|
||||||
lovetheguitar
|
|
||||||
Lukas Bednar
|
Lukas Bednar
|
||||||
Luke Murphy
|
Luke Murphy
|
||||||
Maciek Fijalkowski
|
Maciek Fijalkowski
|
||||||
|
|
@ -262,7 +258,6 @@ Marc Bresson
|
||||||
Marco Gorelli
|
Marco Gorelli
|
||||||
Mark Abramowitz
|
Mark Abramowitz
|
||||||
Mark Dickinson
|
Mark Dickinson
|
||||||
Mark Vong
|
|
||||||
Marko Pacak
|
Marko Pacak
|
||||||
Markus Unterwaditzer
|
Markus Unterwaditzer
|
||||||
Martijn Faassen
|
Martijn Faassen
|
||||||
|
|
@ -283,7 +278,6 @@ Michael Droettboom
|
||||||
Michael Goerz
|
Michael Goerz
|
||||||
Michael Krebs
|
Michael Krebs
|
||||||
Michael Seifert
|
Michael Seifert
|
||||||
Michael Vogt
|
|
||||||
Michal Wajszczuk
|
Michal Wajszczuk
|
||||||
Michał Górny
|
Michał Górny
|
||||||
Michał Zięba
|
Michał Zięba
|
||||||
|
|
@ -295,7 +289,6 @@ Mike Lundy
|
||||||
Milan Lesnek
|
Milan Lesnek
|
||||||
Miro Hrončok
|
Miro Hrončok
|
||||||
mrbean-bremen
|
mrbean-bremen
|
||||||
Nathan Goldbaum
|
|
||||||
Nathaniel Compton
|
Nathaniel Compton
|
||||||
Nathaniel Waisbrot
|
Nathaniel Waisbrot
|
||||||
Ned Batchelder
|
Ned Batchelder
|
||||||
|
|
@ -305,7 +298,6 @@ Nicholas Devenish
|
||||||
Nicholas Murphy
|
Nicholas Murphy
|
||||||
Niclas Olofsson
|
Niclas Olofsson
|
||||||
Nicolas Delaby
|
Nicolas Delaby
|
||||||
Nico Vidal
|
|
||||||
Nikolay Kondratyev
|
Nikolay Kondratyev
|
||||||
Nipunn Koorapati
|
Nipunn Koorapati
|
||||||
Oleg Pidsadnyi
|
Oleg Pidsadnyi
|
||||||
|
|
@ -366,7 +358,6 @@ Sadra Barikbin
|
||||||
Saiprasad Kale
|
Saiprasad Kale
|
||||||
Samuel Colvin
|
Samuel Colvin
|
||||||
Samuel Dion-Girardeau
|
Samuel Dion-Girardeau
|
||||||
Samuel Jirovec
|
|
||||||
Samuel Searles-Bryant
|
Samuel Searles-Bryant
|
||||||
Samuel Therrien (Avasam)
|
Samuel Therrien (Avasam)
|
||||||
Samuele Pedroni
|
Samuele Pedroni
|
||||||
|
|
@ -395,7 +386,6 @@ Stefano Taschini
|
||||||
Steffen Allner
|
Steffen Allner
|
||||||
Stephan Obermann
|
Stephan Obermann
|
||||||
Sven-Hendrik Haase
|
Sven-Hendrik Haase
|
||||||
Sviatoslav Sydorenko
|
|
||||||
Sylvain Marié
|
Sylvain Marié
|
||||||
Tadek Teleżyński
|
Tadek Teleżyński
|
||||||
Takafumi Arakaki
|
Takafumi Arakaki
|
||||||
|
|
@ -430,7 +420,6 @@ Victor Rodriguez
|
||||||
Victor Uriarte
|
Victor Uriarte
|
||||||
Vidar T. Fauske
|
Vidar T. Fauske
|
||||||
Vijay Arora
|
Vijay Arora
|
||||||
Virendra Patil
|
|
||||||
Virgil Dupras
|
Virgil Dupras
|
||||||
Vitaly Lashmanov
|
Vitaly Lashmanov
|
||||||
Vivaan Verma
|
Vivaan Verma
|
||||||
|
|
@ -455,7 +444,6 @@ Yusuke Kadowaki
|
||||||
Yutian Li
|
Yutian Li
|
||||||
Yuval Shimon
|
Yuval Shimon
|
||||||
Zac Hatfield-Dodds
|
Zac Hatfield-Dodds
|
||||||
Zach Snicker
|
|
||||||
Zachary Kneupper
|
Zachary Kneupper
|
||||||
Zachary OBrien
|
Zachary OBrien
|
||||||
Zhouxin Qiu
|
Zhouxin Qiu
|
||||||
|
|
|
||||||
|
|
@ -1,10 +1,14 @@
|
||||||
============================
|
============================
|
||||||
Contributing
|
Contribution getting started
|
||||||
============================
|
============================
|
||||||
|
|
||||||
Contributions are highly welcomed and appreciated. Every little bit of help counts,
|
Contributions are highly welcomed and appreciated. Every little bit of help counts,
|
||||||
so do not hesitate!
|
so do not hesitate!
|
||||||
|
|
||||||
|
.. contents::
|
||||||
|
:depth: 2
|
||||||
|
:backlinks: none
|
||||||
|
|
||||||
|
|
||||||
.. _submitfeedback:
|
.. _submitfeedback:
|
||||||
|
|
||||||
|
|
@ -124,7 +128,7 @@ For example:
|
||||||
Submitting Plugins to pytest-dev
|
Submitting Plugins to pytest-dev
|
||||||
--------------------------------
|
--------------------------------
|
||||||
|
|
||||||
Development of the pytest core, support code, and some plugins happens
|
Pytest development of the core, some plugins and support code happens
|
||||||
in repositories living under the ``pytest-dev`` organisations:
|
in repositories living under the ``pytest-dev`` organisations:
|
||||||
|
|
||||||
- `pytest-dev on GitHub <https://github.com/pytest-dev>`_
|
- `pytest-dev on GitHub <https://github.com/pytest-dev>`_
|
||||||
|
|
|
||||||
|
|
@ -1,5 +1,3 @@
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
import sys
|
import sys
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -2,8 +2,6 @@
|
||||||
# 2.7.5 3.3.2
|
# 2.7.5 3.3.2
|
||||||
# FilesCompleter 75.1109 69.2116
|
# FilesCompleter 75.1109 69.2116
|
||||||
# FastFilesCompleter 0.7383 1.0760
|
# FastFilesCompleter 0.7383 1.0760
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
import timeit
|
import timeit
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,5 +1,2 @@
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
|
|
||||||
for i in range(1000):
|
for i in range(1000):
|
||||||
exec("def test_func_%d(): pass" % i)
|
exec("def test_func_%d(): pass" % i)
|
||||||
|
|
|
||||||
|
|
@ -1,5 +1,3 @@
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
import pytest
|
import pytest
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,5 +1,3 @@
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
import pytest
|
import pytest
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,5 +1,3 @@
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
from unittest import TestCase # noqa: F401
|
from unittest import TestCase # noqa: F401
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,6 +1,3 @@
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
|
|
||||||
for i in range(5000):
|
for i in range(5000):
|
||||||
exec(
|
exec(
|
||||||
f"""
|
f"""
|
||||||
|
|
|
||||||
|
|
@ -1,34 +0,0 @@
|
||||||
*
|
|
||||||
!.gitignore
|
|
||||||
!_template.rst
|
|
||||||
!README.rst
|
|
||||||
!*.bugfix
|
|
||||||
!*.bugfix.rst
|
|
||||||
!*.bugfix.*.rst
|
|
||||||
!*.breaking
|
|
||||||
!*.breaking.rst
|
|
||||||
!*.breaking.*.rst
|
|
||||||
!*.contrib
|
|
||||||
!*.contrib.rst
|
|
||||||
!*.contrib.*.rst
|
|
||||||
!*.deprecation
|
|
||||||
!*.deprecation.rst
|
|
||||||
!*.deprecation.*.rst
|
|
||||||
!*.doc
|
|
||||||
!*.doc.rst
|
|
||||||
!*.doc.*.rst
|
|
||||||
!*.feature
|
|
||||||
!*.feature.rst
|
|
||||||
!*.feature.*.rst
|
|
||||||
!*.improvement
|
|
||||||
!*.improvement.rst
|
|
||||||
!*.improvement.*.rst
|
|
||||||
!*.misc
|
|
||||||
!*.misc.rst
|
|
||||||
!*.misc.*.rst
|
|
||||||
!*.packaging
|
|
||||||
!*.packaging.rst
|
|
||||||
!*.packaging.*.rst
|
|
||||||
!*.vendor
|
|
||||||
!*.vendor.rst
|
|
||||||
!*.vendor.*.rst
|
|
||||||
|
|
@ -1 +0,0 @@
|
||||||
:func:`pytest.approx` now correctly handles :class:`Sequence <collections.abc.Sequence>`-like objects.
|
|
||||||
|
|
@ -0,0 +1 @@
|
||||||
|
Fix `PermissionError` crashes arising from directories which are not selected on the command-line.
|
||||||
|
|
@ -0,0 +1 @@
|
||||||
|
Keyboard interrupts and system exits are now properly handled during the test collection.
|
||||||
|
|
@ -1,11 +1,7 @@
|
||||||
Fixed a regression in pytest 8.0 where tracebacks get longer and longer when multiple
|
Fix a regression in pytest 8.0 where tracebacks get longer and longer when multiple tests fail due to a shared higher-scope fixture which raised.
|
||||||
tests fail due to a shared higher-scope fixture which raised -- by :user:`bluetech`.
|
|
||||||
|
|
||||||
Also fixed a similar regression in pytest 5.4 for collectors which raise during setup.
|
Also fix a similar regression in pytest 5.4 for collectors which raise during setup.
|
||||||
|
|
||||||
The fix necessitated internal changes which may affect some plugins:
|
The fix necessitated internal changes which may affect some plugins:
|
||||||
|
- ``FixtureDef.cached_result[2]`` is now a tuple ``(exc, tb)`` instead of ``exc``.
|
||||||
* ``FixtureDef.cached_result[2]`` is now a tuple ``(exc, tb)``
|
- ``SetupState.stack`` failures are now a tuple ``(exc, tb)`` instead of ``exc``.
|
||||||
instead of ``exc``.
|
|
||||||
* ``SetupState.stack`` failures are now a tuple ``(exc, tb)``
|
|
||||||
instead of ``exc``.
|
|
||||||
|
|
|
||||||
|
|
@ -1 +0,0 @@
|
||||||
12204.bugfix.rst
|
|
||||||
|
|
@ -1,8 +0,0 @@
|
||||||
Added support for keyword matching in marker expressions.
|
|
||||||
|
|
||||||
Now tests can be selected by marker keyword arguments.
|
|
||||||
Supported values are :class:`int`, (unescaped) :class:`str`, :class:`bool` & :data:`None`.
|
|
||||||
|
|
||||||
See :ref:`marker examples <marker_keyword_expression_example>` for more information.
|
|
||||||
|
|
||||||
-- by :user:`lovetheguitar`
|
|
||||||
|
|
@ -0,0 +1 @@
|
||||||
|
Fixed handling of 'Function not implemented' error under squashfuse_ll, which is a different way to say that the mountpoint is read-only.
|
||||||
|
|
@ -1 +0,0 @@
|
||||||
Fix a regression in pytest 8.0.0 where package-scoped parameterized items were not correctly reordered to minimize setups/teardowns in some cases.
|
|
||||||
|
|
@ -1 +0,0 @@
|
||||||
Fix crash with `assert testcase is not None` assertion failure when re-running unittest tests using plugins like pytest-rerunfailures. Regressed in 8.2.2.
|
|
||||||
|
|
@ -1,3 +0,0 @@
|
||||||
Migrated all internal type-annotations to the python3.10+ style by using the `annotations` future import.
|
|
||||||
|
|
||||||
-- by :user:`RonnyPfannschmidt`
|
|
||||||
|
|
@ -1,6 +0,0 @@
|
||||||
The external plugin mentions in the documentation now avoid mentioning
|
|
||||||
:std:doc:`setuptools entry-points <setuptools:index>` as the concept is
|
|
||||||
much more generic nowadays. Instead, the terminology of "external",
|
|
||||||
"installed", or "third-party" plugins (or packages) replaces that.
|
|
||||||
|
|
||||||
-- by :user:`webknjaz`
|
|
||||||
|
|
@ -1,4 +0,0 @@
|
||||||
The console output now uses the "third-party plugins" terminology,
|
|
||||||
replacing the previously established but confusing and outdated
|
|
||||||
reference to :std:doc:`setuptools <setuptools:index>`
|
|
||||||
-- by :user:`webknjaz`.
|
|
||||||
|
|
@ -1 +0,0 @@
|
||||||
Fixed a crash when returning category ``"error"`` or ``"failed"`` with a custom test status from :hook:`pytest_report_teststatus` hook -- :user:`pbrezina`.
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
The change log draft preview integration has been refactored to use a
|
|
||||||
third party extension ``sphinxcontib-towncrier``. The previous in-repo
|
|
||||||
script was putting the change log preview file at
|
|
||||||
:file:`doc/en/_changelog_towncrier_draft.rst`. Said file is no longer
|
|
||||||
ignored in Git and might show up among untracked files in the
|
|
||||||
development environments of the contributors. To address that, the
|
|
||||||
contributors can run the following command that will clean it up:
|
|
||||||
|
|
||||||
.. code-block:: console
|
|
||||||
|
|
||||||
$ git clean -x -i -- doc/en/_changelog_towncrier_draft.rst
|
|
||||||
|
|
||||||
-- by :user:`webknjaz`
|
|
||||||
|
|
@ -1,5 +0,0 @@
|
||||||
All the undocumented ``tox`` environments now have descriptions.
|
|
||||||
They can be listed in one's development environment by invoking
|
|
||||||
``tox -av`` in a terminal.
|
|
||||||
|
|
||||||
-- by :user:`webknjaz`
|
|
||||||
|
|
@ -1,11 +0,0 @@
|
||||||
The changelog configuration has been updated to introduce more accurate
|
|
||||||
audience-tailored categories. Previously, there was a ``trivial``
|
|
||||||
change log fragment type with an unclear and broad meaning. It was
|
|
||||||
removed and we now have ``contrib``, ``misc`` and ``packaging`` in
|
|
||||||
place of it.
|
|
||||||
|
|
||||||
The new change note types target the readers who are downstream
|
|
||||||
packagers and project contributors. Additionally, the miscellaneous
|
|
||||||
section is kept for unspecified updates that do not fit anywhere else.
|
|
||||||
|
|
||||||
-- by :user:`webknjaz`
|
|
||||||
|
|
@ -1,7 +0,0 @@
|
||||||
The UX of the GitHub automation making pull requests to update the
|
|
||||||
plugin list has been updated. Previously, the maintainers had to close
|
|
||||||
the automatically created pull requests and re-open them to trigger the
|
|
||||||
CI runs. From now on, they only need to click the `Ready for review`
|
|
||||||
button instead.
|
|
||||||
|
|
||||||
-- by :user:`webknjaz`
|
|
||||||
|
|
@ -1 +0,0 @@
|
||||||
Improve handling of invalid regex patterns in :func:`pytest.raises(match=r'...') <pytest.raises>` by providing a clear error message.
|
|
||||||
|
|
@ -1,4 +0,0 @@
|
||||||
The ``:pull:`` RST role has been replaced with a shorter
|
|
||||||
``:pr:`` due to starting to use the implementation from
|
|
||||||
the third-party :pypi:`sphinx-issues` Sphinx extension
|
|
||||||
-- by :user:`webknjaz`.
|
|
||||||
|
|
@ -1,6 +0,0 @@
|
||||||
The coverage reporting configuration has been updated to exclude
|
|
||||||
pytest's own tests marked as expected to fail from the coverage
|
|
||||||
report. This has an effect of reducing the influence of flaky
|
|
||||||
tests on the resulting number.
|
|
||||||
|
|
||||||
-- by :user:`webknjaz`
|
|
||||||
|
|
@ -1,7 +0,0 @@
|
||||||
The ``extlinks`` Sphinx extension is no longer enabled. The ``:bpo:``
|
|
||||||
role it used to declare has been removed with that. BPO itself has
|
|
||||||
migrated to GitHub some years ago and it is possible to link the
|
|
||||||
respective issues by using their GitHub issue numbers and the
|
|
||||||
``:issue:`` role that the ``sphinx-issues`` extension implements.
|
|
||||||
|
|
||||||
-- by :user:`webknjaz`
|
|
||||||
|
|
@ -1,3 +0,0 @@
|
||||||
The ``_in_venv()`` function now detects Python virtual environments by
|
|
||||||
checking for a :file:`pyvenv.cfg` file, ensuring reliable detection on
|
|
||||||
various platforms -- by :user:`zachsnickers`.
|
|
||||||
|
|
@ -1 +0,0 @@
|
||||||
12544.improvement.rst
|
|
||||||
|
|
@ -1,2 +0,0 @@
|
||||||
Possible typos in using the ``:user:`` RST role is now being linted
|
|
||||||
through the pre-commit tool integration -- by :user:`webknjaz`.
|
|
||||||
|
|
@ -1 +0,0 @@
|
||||||
Do not truncate arguments to functions in output when running with `-vvv`.
|
|
||||||
|
|
@ -1,38 +0,0 @@
|
||||||
The readability of assertion introspection of bound methods has been enhanced
|
|
||||||
-- by :user:`farbodahm`, :user:`webknjaz`, :user:`obestwalter`, :user:`flub`
|
|
||||||
and :user:`glyphack`.
|
|
||||||
|
|
||||||
Earlier, it was like:
|
|
||||||
|
|
||||||
.. code-block:: console
|
|
||||||
|
|
||||||
=================================== FAILURES ===================================
|
|
||||||
_____________________________________ test _____________________________________
|
|
||||||
|
|
||||||
def test():
|
|
||||||
> assert Help().fun() == 2
|
|
||||||
E assert 1 == 2
|
|
||||||
E + where 1 = <bound method Help.fun of <example.Help instance at 0x256a830>>()
|
|
||||||
E + where <bound method Help.fun of <example.Help instance at 0x256a830>> = <example.Help instance at 0x256a830>.fun
|
|
||||||
E + where <example.Help instance at 0x256a830> = Help()
|
|
||||||
|
|
||||||
example.py:7: AssertionError
|
|
||||||
=========================== 1 failed in 0.03 seconds ===========================
|
|
||||||
|
|
||||||
|
|
||||||
And now it's like:
|
|
||||||
|
|
||||||
.. code-block:: console
|
|
||||||
|
|
||||||
=================================== FAILURES ===================================
|
|
||||||
_____________________________________ test _____________________________________
|
|
||||||
|
|
||||||
def test():
|
|
||||||
> assert Help().fun() == 2
|
|
||||||
E assert 1 == 2
|
|
||||||
E + where 1 = fun()
|
|
||||||
E + where fun = <test_local.Help object at 0x1074be230>.fun
|
|
||||||
E + where <test_local.Help object at 0x1074be230> = Help()
|
|
||||||
|
|
||||||
test_local.py:13: AssertionError
|
|
||||||
=========================== 1 failed in 0.03 seconds ===========================
|
|
||||||
|
|
@ -1 +0,0 @@
|
||||||
Added timezone information to the testsuite timestamp in the JUnit XML report.
|
|
||||||
|
|
@ -20,22 +20,10 @@ Each file should be named like ``<ISSUE>.<TYPE>.rst``, where
|
||||||
* ``deprecation``: feature deprecation.
|
* ``deprecation``: feature deprecation.
|
||||||
* ``breaking``: a change which may break existing suites, such as feature removal or behavior change.
|
* ``breaking``: a change which may break existing suites, such as feature removal or behavior change.
|
||||||
* ``vendor``: changes in packages vendored in pytest.
|
* ``vendor``: changes in packages vendored in pytest.
|
||||||
* ``packaging``: notes for downstreams about unobvious side effects
|
* ``trivial``: fixing a small typo or internal change that might be noteworthy.
|
||||||
and tooling. changes in the test invocation considerations and
|
|
||||||
runtime assumptions.
|
|
||||||
* ``contrib``: stuff that affects the contributor experience. e.g.
|
|
||||||
Running tests, building the docs, setting up the development
|
|
||||||
environment.
|
|
||||||
* ``misc``: changes that are hard to assign to any of the above
|
|
||||||
categories.
|
|
||||||
|
|
||||||
So for example: ``123.feature.rst``, ``456.bugfix.rst``.
|
So for example: ``123.feature.rst``, ``456.bugfix.rst``.
|
||||||
|
|
||||||
.. tip::
|
|
||||||
|
|
||||||
See :file:`pyproject.toml` for all available categories
|
|
||||||
(``tool.towncrier.type``).
|
|
||||||
|
|
||||||
If your PR fixes an issue, use that number here. If there is no issue,
|
If your PR fixes an issue, use that number here. If there is no issue,
|
||||||
then after you submit the PR and get the PR number you can add a
|
then after you submit the PR and get the PR number you can add a
|
||||||
changelog using that instead.
|
changelog using that instead.
|
||||||
|
|
|
||||||
|
|
@ -1,9 +1,4 @@
|
||||||
# reference: https://docs.codecov.io/docs/codecovyml-reference
|
# reference: https://docs.codecov.io/docs/codecovyml-reference
|
||||||
---
|
|
||||||
|
|
||||||
codecov:
|
|
||||||
token: 1eca3b1f-31a2-4fb8-a8c3-138b441b50a7 #repo token
|
|
||||||
|
|
||||||
coverage:
|
coverage:
|
||||||
status:
|
status:
|
||||||
patch: true
|
patch: true
|
||||||
|
|
|
||||||
|
|
@ -1,7 +0,0 @@
|
||||||
<style>
|
|
||||||
.logo {text-align: center;}
|
|
||||||
</style>
|
|
||||||
|
|
||||||
<a class="logo" href="{{ pathto('contents') }}">
|
|
||||||
<img src="{{ pathto('_static/pytest1.png', 1) }}" width="70%" height="70%" text="Pytest Logo"/>
|
|
||||||
</a>
|
|
||||||
|
|
@ -0,0 +1,14 @@
|
||||||
|
{#
|
||||||
|
basic/searchbox.html with heading removed.
|
||||||
|
#}
|
||||||
|
{%- if pagename != "search" and builder != "singlehtml" %}
|
||||||
|
<div id="searchbox" style="display: none" role="search">
|
||||||
|
<div class="searchformwrapper">
|
||||||
|
<form class="search" action="{{ pathto('search') }}" method="get">
|
||||||
|
<input type="text" name="q" aria-labelledby="searchlabel" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false"/>
|
||||||
|
<input type="submit" value="{{ _('Go') }}" />
|
||||||
|
</form>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<script>document.getElementById('searchbox').style.display = "block"</script>
|
||||||
|
{%- endif %}
|
||||||
|
|
@ -1,7 +0,0 @@
|
||||||
<style>
|
|
||||||
ul {list-style: none;}
|
|
||||||
li {margin: 0.4em 0;}
|
|
||||||
@media (min-width: 46em) {
|
|
||||||
#features {width: 50%;}
|
|
||||||
}
|
|
||||||
</style>
|
|
||||||
|
|
@ -6,8 +6,6 @@ Release announcements
|
||||||
:maxdepth: 2
|
:maxdepth: 2
|
||||||
|
|
||||||
|
|
||||||
release-8.2.2
|
|
||||||
release-8.2.1
|
|
||||||
release-8.2.0
|
release-8.2.0
|
||||||
release-8.1.2
|
release-8.1.2
|
||||||
release-8.1.1
|
release-8.1.1
|
||||||
|
|
|
||||||
|
|
@ -62,7 +62,7 @@ New Features
|
||||||
- new "-q" option which decreases verbosity and prints a more
|
- new "-q" option which decreases verbosity and prints a more
|
||||||
nose/unittest-style "dot" output.
|
nose/unittest-style "dot" output.
|
||||||
|
|
||||||
- many, many, more detailed improvements details
|
- many many more detailed improvements details
|
||||||
|
|
||||||
Fixes
|
Fixes
|
||||||
-----------------------
|
-----------------------
|
||||||
|
|
@ -109,7 +109,7 @@ Important Notes
|
||||||
in conftest.py files. They will cause nothing special.
|
in conftest.py files. They will cause nothing special.
|
||||||
- removed support for calling the pre-1.0 collection API of "run()" and "join"
|
- removed support for calling the pre-1.0 collection API of "run()" and "join"
|
||||||
- removed reading option values from conftest.py files or env variables.
|
- removed reading option values from conftest.py files or env variables.
|
||||||
This can now be done much, much, better and easier through the ini-file
|
This can now be done much much better and easier through the ini-file
|
||||||
mechanism and the "addopts" entry in particular.
|
mechanism and the "addopts" entry in particular.
|
||||||
- removed the "disabled" attribute in test classes. Use the skipping
|
- removed the "disabled" attribute in test classes. Use the skipping
|
||||||
and pytestmark mechanism to skip or xfail a test class.
|
and pytestmark mechanism to skip or xfail a test class.
|
||||||
|
|
|
||||||
|
|
@ -4,7 +4,7 @@ pytest-2.2.2: bug fixes
|
||||||
pytest-2.2.2 (updated to 2.2.3 to fix packaging issues) is a minor
|
pytest-2.2.2 (updated to 2.2.3 to fix packaging issues) is a minor
|
||||||
backward-compatible release of the versatile py.test testing tool. It
|
backward-compatible release of the versatile py.test testing tool. It
|
||||||
contains bug fixes and a few refinements particularly to reporting with
|
contains bug fixes and a few refinements particularly to reporting with
|
||||||
"--collectonly", see below for details.
|
"--collectonly", see below for betails.
|
||||||
|
|
||||||
For general information see here:
|
For general information see here:
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -181,7 +181,7 @@ Bug fixes:
|
||||||
partially failed (finalizers would not always be called before)
|
partially failed (finalizers would not always be called before)
|
||||||
|
|
||||||
- fix issue320 - fix class scope for fixtures when mixed with
|
- fix issue320 - fix class scope for fixtures when mixed with
|
||||||
module-level functions. Thanks Anatoly Bubenkoff.
|
module-level functions. Thanks Anatloy Bubenkoff.
|
||||||
|
|
||||||
- you can specify "-q" or "-qq" to get different levels of "quieter"
|
- you can specify "-q" or "-qq" to get different levels of "quieter"
|
||||||
reporting (thanks Katarzyna Jachim)
|
reporting (thanks Katarzyna Jachim)
|
||||||
|
|
|
||||||
|
|
@ -83,7 +83,7 @@ holger krekel
|
||||||
Thanks Ralph Schmitt for the precise failure example.
|
Thanks Ralph Schmitt for the precise failure example.
|
||||||
|
|
||||||
- fix issue244 by implementing special index for parameters to only use
|
- fix issue244 by implementing special index for parameters to only use
|
||||||
indices for parametrized test ids
|
indices for paramentrized test ids
|
||||||
|
|
||||||
- fix issue287 by running all finalizers but saving the exception
|
- fix issue287 by running all finalizers but saving the exception
|
||||||
from the first failing finalizer and re-raising it so teardown will
|
from the first failing finalizer and re-raising it so teardown will
|
||||||
|
|
|
||||||
|
|
@ -73,7 +73,7 @@ holger krekel
|
||||||
- cleanup setup.py a bit and specify supported versions. Thanks Jurko
|
- cleanup setup.py a bit and specify supported versions. Thanks Jurko
|
||||||
Gospodnetic for the PR.
|
Gospodnetic for the PR.
|
||||||
|
|
||||||
- change XPASS colour to yellow rather than red when tests are run
|
- change XPASS colour to yellow rather then red when tests are run
|
||||||
with -v.
|
with -v.
|
||||||
|
|
||||||
- fix issue473: work around mock putting an unbound method into a class
|
- fix issue473: work around mock putting an unbound method into a class
|
||||||
|
|
|
||||||
|
|
@ -55,7 +55,7 @@ holger krekel
|
||||||
github. See https://pytest.org/en/stable/contributing.html .
|
github. See https://pytest.org/en/stable/contributing.html .
|
||||||
Thanks to Anatoly for pushing and initial work on this.
|
Thanks to Anatoly for pushing and initial work on this.
|
||||||
|
|
||||||
- fix issue650: new option ``--doctest-ignore-import-errors`` which
|
- fix issue650: new option ``--docttest-ignore-import-errors`` which
|
||||||
will turn import errors in doctests into skips. Thanks Charles Cloud
|
will turn import errors in doctests into skips. Thanks Charles Cloud
|
||||||
for the complete PR.
|
for the complete PR.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -45,7 +45,7 @@ The py.test Development Team
|
||||||
**New Features**
|
**New Features**
|
||||||
|
|
||||||
* New ``pytest.mark.skip`` mark, which unconditionally skips marked tests.
|
* New ``pytest.mark.skip`` mark, which unconditionally skips marked tests.
|
||||||
Thanks :user:`MichaelAquilina` for the complete PR (:pr:`1040`).
|
Thanks :user:`MichaelAquilina` for the complete PR (:pull:`1040`).
|
||||||
|
|
||||||
* ``--doctest-glob`` may now be passed multiple times in the command-line.
|
* ``--doctest-glob`` may now be passed multiple times in the command-line.
|
||||||
Thanks :user:`jab` and :user:`nicoddemus` for the PR.
|
Thanks :user:`jab` and :user:`nicoddemus` for the PR.
|
||||||
|
|
|
||||||
|
|
@ -44,7 +44,7 @@ The py.test Development Team
|
||||||
Thanks :user:`nicoddemus` for the PR.
|
Thanks :user:`nicoddemus` for the PR.
|
||||||
|
|
||||||
* Fix (:issue:`469`): junit parses report.nodeid incorrectly, when params IDs
|
* Fix (:issue:`469`): junit parses report.nodeid incorrectly, when params IDs
|
||||||
contain ``::``. Thanks :user:`tomviner` for the PR (:pr:`1431`).
|
contain ``::``. Thanks :user:`tomviner` for the PR (:pull:`1431`).
|
||||||
|
|
||||||
* Fix (:issue:`578`): SyntaxErrors
|
* Fix (:issue:`578`): SyntaxErrors
|
||||||
containing non-ascii lines at the point of failure generated an internal
|
containing non-ascii lines at the point of failure generated an internal
|
||||||
|
|
|
||||||
|
|
@ -44,14 +44,14 @@ The py.test Development Team
|
||||||
|
|
||||||
* Fix Xfail does not work with condition keyword argument.
|
* Fix Xfail does not work with condition keyword argument.
|
||||||
Thanks :user:`astraw38` for reporting the issue (:issue:`1496`) and :user:`tomviner`
|
Thanks :user:`astraw38` for reporting the issue (:issue:`1496`) and :user:`tomviner`
|
||||||
for PR the (:pr:`1524`).
|
for PR the (:pull:`1524`).
|
||||||
|
|
||||||
* Fix win32 path issue when putting custom config file with absolute path
|
* Fix win32 path issue when putting custom config file with absolute path
|
||||||
in ``pytest.main("-c your_absolute_path")``.
|
in ``pytest.main("-c your_absolute_path")``.
|
||||||
|
|
||||||
* Fix maximum recursion depth detection when raised error class is not aware
|
* Fix maximum recursion depth detection when raised error class is not aware
|
||||||
of unicode/encoded bytes.
|
of unicode/encoded bytes.
|
||||||
Thanks :user:`prusse-martin` for the PR (:pr:`1506`).
|
Thanks :user:`prusse-martin` for the PR (:pull:`1506`).
|
||||||
|
|
||||||
* Fix ``pytest.mark.skip`` mark when used in strict mode.
|
* Fix ``pytest.mark.skip`` mark when used in strict mode.
|
||||||
Thanks :user:`pquentin` for the PR and :user:`RonnyPfannschmidt` for
|
Thanks :user:`pquentin` for the PR and :user:`RonnyPfannschmidt` for
|
||||||
|
|
|
||||||
|
|
@ -1,19 +0,0 @@
|
||||||
pytest-8.2.1
|
|
||||||
=======================================
|
|
||||||
|
|
||||||
pytest 8.2.1 has just been released to PyPI.
|
|
||||||
|
|
||||||
This is a bug-fix release, being a drop-in replacement. To upgrade::
|
|
||||||
|
|
||||||
pip install --upgrade pytest
|
|
||||||
|
|
||||||
The full changelog is available at https://docs.pytest.org/en/stable/changelog.html.
|
|
||||||
|
|
||||||
Thanks to all of the contributors to this release:
|
|
||||||
|
|
||||||
* Bruno Oliveira
|
|
||||||
* Ran Benita
|
|
||||||
|
|
||||||
|
|
||||||
Happy testing,
|
|
||||||
The pytest Development Team
|
|
||||||
|
|
@ -1,19 +0,0 @@
|
||||||
pytest-8.2.2
|
|
||||||
=======================================
|
|
||||||
|
|
||||||
pytest 8.2.2 has just been released to PyPI.
|
|
||||||
|
|
||||||
This is a bug-fix release, being a drop-in replacement. To upgrade::
|
|
||||||
|
|
||||||
pip install --upgrade pytest
|
|
||||||
|
|
||||||
The full changelog is available at https://docs.pytest.org/en/stable/changelog.html.
|
|
||||||
|
|
||||||
Thanks to all of the contributors to this release:
|
|
||||||
|
|
||||||
* Bruno Oliveira
|
|
||||||
* Ran Benita
|
|
||||||
|
|
||||||
|
|
||||||
Happy testing,
|
|
||||||
The pytest Development Team
|
|
||||||
|
|
@ -49,7 +49,7 @@ place on 20th, 21st, 22nd, 24th and 25th. On the 23rd we took a break
|
||||||
day for some hot hiking in the Black Forest.
|
day for some hot hiking in the Black Forest.
|
||||||
|
|
||||||
Sprint activity was organised heavily around pairing, with plenty of group
|
Sprint activity was organised heavily around pairing, with plenty of group
|
||||||
discussions to take advantage of the high bandwidth, and lightning talks
|
discusssions to take advantage of the high bandwidth, and lightning talks
|
||||||
as well.
|
as well.
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -5,26 +5,30 @@ Backwards Compatibility Policy
|
||||||
|
|
||||||
.. versionadded: 6.0
|
.. versionadded: 6.0
|
||||||
|
|
||||||
Pytest is an actively evolving project that has been decades in the making.
|
pytest is actively evolving and is a project that has been decades in the making,
|
||||||
We keep learning about new and better structures to express different details about testing.
|
we keep learning about new and better structures to express different details about testing.
|
||||||
|
|
||||||
While we implement those modifications, we try to ensure an easy transition and don't want to impose unnecessary churn on our users and community/plugin authors.
|
While we implement those modifications we try to ensure an easy transition and don't want to impose unnecessary churn on our users and community/plugin authors.
|
||||||
|
|
||||||
As of now, pytest considers multiple types of backward compatibility transitions:
|
As of now, pytest considers multiple types of backward compatibility transitions:
|
||||||
|
|
||||||
a) trivial: APIs that trivially translate to the new mechanism and do not cause problematic changes.
|
a) trivial: APIs which trivially translate to the new mechanism,
|
||||||
|
and do not cause problematic changes.
|
||||||
|
|
||||||
We try to support those indefinitely while encouraging users to switch to newer or better mechanisms through documentation.
|
We try to support those indefinitely while encouraging users to switch to newer/better mechanisms through documentation.
|
||||||
|
|
||||||
b) transitional: the old and new APIs don't conflict, and we can help users transition by using warnings while supporting both for a prolonged period of time.
|
b) transitional: the old and new API don't conflict
|
||||||
|
and we can help users transition by using warnings, while supporting both for a prolonged time.
|
||||||
|
|
||||||
We will only start the removal of deprecated functionality in major releases (e.g., if we deprecate something in 3.0, we will start to remove it in 4.0), and keep it around for at least two minor releases (e.g., if we deprecate something in 3.9 and 4.0 is the next release, we start to remove it in 5.0, not in 4.0).
|
We will only start the removal of deprecated functionality in major releases (e.g. if we deprecate something in 3.0 we will start to remove it in 4.0), and keep it around for at least two minor releases (e.g. if we deprecate something in 3.9 and 4.0 is the next release, we start to remove it in 5.0, not in 4.0).
|
||||||
|
|
||||||
A deprecated feature scheduled to be removed in major version X will use the warning class `PytestRemovedInXWarning` (a subclass of :class:`~pytest.PytestDeprecationWarning`).
|
A deprecated feature scheduled to be removed in major version X will use the warning class `PytestRemovedInXWarning` (a subclass of :class:`~pytest.PytestDeprecationWarning`).
|
||||||
|
|
||||||
When the deprecation expires (e.g., 4.0 is released), we won't remove the deprecated functionality immediately but will use the standard warning filters to turn `PytestRemovedInXWarning` (e.g., `PytestRemovedIn4Warning`) into **errors** by default. This approach makes it explicit that removal is imminent and still gives you time to turn the deprecated feature into a warning instead of an error so it can be dealt with in your own time. In the next minor release (e.g., 4.1), the feature will be effectively removed.
|
When the deprecation expires (e.g. 4.0 is released), we won't remove the deprecated functionality immediately, but will use the standard warning filters to turn `PytestRemovedInXWarning` (e.g. `PytestRemovedIn4Warning`) into **errors** by default. This approach makes it explicit that removal is imminent, and still gives you time to turn the deprecated feature into a warning instead of an error so it can be dealt with in your own time. In the next minor release (e.g. 4.1), the feature will be effectively removed.
|
||||||
|
|
||||||
c) True breakage should only be considered when a normal transition is unreasonably unsustainable and would offset important developments or features by years. In addition, they should be limited to APIs where the number of actual users is very small (for example, only impacting some plugins) and can be coordinated with the community in advance.
|
|
||||||
|
c) true breakage: should only be considered when normal transition is unreasonably unsustainable and would offset important development/features by years.
|
||||||
|
In addition, they should be limited to APIs where the number of actual users is very small (for example only impacting some plugins), and can be coordinated with the community in advance.
|
||||||
|
|
||||||
Examples for such upcoming changes:
|
Examples for such upcoming changes:
|
||||||
|
|
||||||
|
|
@ -58,11 +62,11 @@ Focus primary on smooth transition - stance (pre 6.0)
|
||||||
|
|
||||||
Keeping backwards compatibility has a very high priority in the pytest project. Although we have deprecated functionality over the years, most of it is still supported. All deprecations in pytest were done because simpler or more efficient ways of accomplishing the same tasks have emerged, making the old way of doing things unnecessary.
|
Keeping backwards compatibility has a very high priority in the pytest project. Although we have deprecated functionality over the years, most of it is still supported. All deprecations in pytest were done because simpler or more efficient ways of accomplishing the same tasks have emerged, making the old way of doing things unnecessary.
|
||||||
|
|
||||||
With the pytest 3.0 release, we introduced a clear communication scheme for when we will actually remove the old busted joint and politely ask you to use the new hotness instead, while giving you enough time to adjust your tests or raise concerns if there are valid reasons to keep deprecated functionality around.
|
With the pytest 3.0 release we introduced a clear communication scheme for when we will actually remove the old busted joint and politely ask you to use the new hotness instead, while giving you enough time to adjust your tests or raise concerns if there are valid reasons to keep deprecated functionality around.
|
||||||
|
|
||||||
To communicate changes, we issue deprecation warnings using a custom warning hierarchy (see :ref:`internal-warnings`). These warnings may be suppressed using the standard means: ``-W`` command-line flag or ``filterwarnings`` ini options (see :ref:`warnings`), but we suggest to use these sparingly and temporarily, and heed the warnings when possible.
|
To communicate changes we issue deprecation warnings using a custom warning hierarchy (see :ref:`internal-warnings`). These warnings may be suppressed using the standard means: ``-W`` command-line flag or ``filterwarnings`` ini options (see :ref:`warnings`), but we suggest to use these sparingly and temporarily, and heed the warnings when possible.
|
||||||
|
|
||||||
We will only start the removal of deprecated functionality in major releases (e.g. if we deprecate something in 3.0, we will start to remove it in 4.0), and keep it around for at least two minor releases (e.g. if we deprecate something in 3.9 and 4.0 is the next release, we start to remove it in 5.0, not in 4.0).
|
We will only start the removal of deprecated functionality in major releases (e.g. if we deprecate something in 3.0 we will start to remove it in 4.0), and keep it around for at least two minor releases (e.g. if we deprecate something in 3.9 and 4.0 is the next release, we start to remove it in 5.0, not in 4.0).
|
||||||
|
|
||||||
When the deprecation expires (e.g. 4.0 is released), we won't remove the deprecated functionality immediately, but will use the standard warning filters to turn them into **errors** by default. This approach makes it explicit that removal is imminent, and still gives you time to turn the deprecated feature into a warning instead of an error so it can be dealt with in your own time. In the next minor release (e.g. 4.1), the feature will be effectively removed.
|
When the deprecation expires (e.g. 4.0 is released), we won't remove the deprecated functionality immediately, but will use the standard warning filters to turn them into **errors** by default. This approach makes it explicit that removal is imminent, and still gives you time to turn the deprecated feature into a warning instead of an error so it can be dealt with in your own time. In the next minor release (e.g. 4.1), the feature will be effectively removed.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -22,7 +22,7 @@ For information about fixtures, see :ref:`fixtures`. To see a complete list of a
|
||||||
cachedir: .pytest_cache
|
cachedir: .pytest_cache
|
||||||
rootdir: /home/sweet/project
|
rootdir: /home/sweet/project
|
||||||
collected 0 items
|
collected 0 items
|
||||||
cache -- .../_pytest/cacheprovider.py:560
|
cache -- .../_pytest/cacheprovider.py:542
|
||||||
Return a cache object that can persist state between testing sessions.
|
Return a cache object that can persist state between testing sessions.
|
||||||
|
|
||||||
cache.get(key, default)
|
cache.get(key, default)
|
||||||
|
|
@ -115,7 +115,7 @@ For information about fixtures, see :ref:`fixtures`. To see a complete list of a
|
||||||
|
|
||||||
For more details: :ref:`doctest_namespace`.
|
For more details: :ref:`doctest_namespace`.
|
||||||
|
|
||||||
pytestconfig [session scope] -- .../_pytest/fixtures.py:1338
|
pytestconfig [session scope] -- .../_pytest/fixtures.py:1335
|
||||||
Session-scoped fixture that returns the session's :class:`pytest.Config`
|
Session-scoped fixture that returns the session's :class:`pytest.Config`
|
||||||
object.
|
object.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -19,100 +19,18 @@ with advance notice in the **Deprecations** section of releases.
|
||||||
we named the news folder changelog
|
we named the news folder changelog
|
||||||
|
|
||||||
|
|
||||||
.. only:: not is_release
|
.. only:: changelog_towncrier_draft
|
||||||
|
|
||||||
To be included in v\ |release| (if present)
|
.. The 'changelog_towncrier_draft' tag is included by our 'tox -e docs',
|
||||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
but not on readthedocs.
|
||||||
|
|
||||||
.. towncrier-draft-entries:: |release| [UNRELEASED DRAFT]
|
.. include:: _changelog_towncrier_draft.rst
|
||||||
|
|
||||||
Released versions
|
|
||||||
^^^^^^^^^^^^^^^^^
|
|
||||||
|
|
||||||
.. towncrier release notes start
|
.. towncrier release notes start
|
||||||
|
|
||||||
pytest 8.2.2 (2024-06-04)
|
|
||||||
=========================
|
|
||||||
|
|
||||||
Bug Fixes
|
|
||||||
---------
|
|
||||||
|
|
||||||
- `#12355 <https://github.com/pytest-dev/pytest/issues/12355>`_: Fix possible catastrophic performance slowdown on a certain parametrization pattern involving many higher-scoped parameters.
|
|
||||||
|
|
||||||
|
|
||||||
- `#12367 <https://github.com/pytest-dev/pytest/issues/12367>`_: Fix a regression in pytest 8.2.0 where unittest class instances (a fresh one is created for each test) were not released promptly on test teardown but only on session teardown.
|
|
||||||
|
|
||||||
|
|
||||||
- `#12381 <https://github.com/pytest-dev/pytest/issues/12381>`_: Fix possible "Directory not empty" crashes arising from concurent cache dir (``.pytest_cache``) creation. Regressed in pytest 8.2.0.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Improved Documentation
|
|
||||||
----------------------
|
|
||||||
|
|
||||||
- `#12290 <https://github.com/pytest-dev/pytest/issues/12290>`_: Updated Sphinx theme to use Furo instead of Flask, enabling Dark mode theme.
|
|
||||||
|
|
||||||
|
|
||||||
- `#12356 <https://github.com/pytest-dev/pytest/issues/12356>`_: Added a subsection to the documentation for debugging flaky tests to mention
|
|
||||||
lack of thread safety in pytest as a possible source of flakyness.
|
|
||||||
|
|
||||||
|
|
||||||
- `#12363 <https://github.com/pytest-dev/pytest/issues/12363>`_: The documentation webpages now links to a canonical version to reduce outdated documentation in search engine results.
|
|
||||||
|
|
||||||
|
|
||||||
pytest 8.2.1 (2024-05-19)
|
|
||||||
=========================
|
|
||||||
|
|
||||||
Improvements
|
|
||||||
------------
|
|
||||||
|
|
||||||
- `#12334 <https://github.com/pytest-dev/pytest/issues/12334>`_: Support for Python 3.13 (beta1 at the time of writing).
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Bug Fixes
|
|
||||||
---------
|
|
||||||
|
|
||||||
- `#12120 <https://github.com/pytest-dev/pytest/issues/12120>`_: Fix `PermissionError` crashes arising from directories which are not selected on the command-line.
|
|
||||||
|
|
||||||
|
|
||||||
- `#12191 <https://github.com/pytest-dev/pytest/issues/12191>`_: Keyboard interrupts and system exits are now properly handled during the test collection.
|
|
||||||
|
|
||||||
|
|
||||||
- `#12300 <https://github.com/pytest-dev/pytest/issues/12300>`_: Fixed handling of 'Function not implemented' error under squashfuse_ll, which is a different way to say that the mountpoint is read-only.
|
|
||||||
|
|
||||||
|
|
||||||
- `#12308 <https://github.com/pytest-dev/pytest/issues/12308>`_: Fix a regression in pytest 8.2.0 where the permissions of automatically-created ``.pytest_cache`` directories became ``rwx------`` instead of the expected ``rwxr-xr-x``.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Trivial/Internal Changes
|
|
||||||
------------------------
|
|
||||||
|
|
||||||
- `#12333 <https://github.com/pytest-dev/pytest/issues/12333>`_: pytest releases are now attested using the recent `Artifact Attestation <https://github.blog/2024-05-02-introducing-artifact-attestations-now-in-public-beta/>`_ support from GitHub, allowing users to verify the provenance of pytest's sdist and wheel artifacts.
|
|
||||||
|
|
||||||
|
|
||||||
pytest 8.2.0 (2024-04-27)
|
pytest 8.2.0 (2024-04-27)
|
||||||
=========================
|
=========================
|
||||||
|
|
||||||
Breaking Changes
|
|
||||||
----------------
|
|
||||||
|
|
||||||
- `#12089 <https://github.com/pytest-dev/pytest/pull/12089>`_: pytest now requires that :class:`unittest.TestCase` subclasses can be instantiated freely using ``MyTestCase('runTest')``.
|
|
||||||
|
|
||||||
If the class doesn't allow this, you may see an error during collection such as ``AttributeError: 'MyTestCase' object has no attribute 'runTest'``.
|
|
||||||
|
|
||||||
Classes which do not override ``__init__``, or do not access the test method in ``__init__`` using ``getattr`` or similar, are unaffected.
|
|
||||||
|
|
||||||
Classes which do should take care to not crash when ``"runTest"`` is given, as is shown in `unittest.TestCases's implementation <https://github.com/python/cpython/blob/51aefc5bf907ddffaaf083ded0de773adcdf08c8/Lib/unittest/case.py#L419-L426>`_.
|
|
||||||
Alternatively, consider using :meth:`setUp <unittest.TestCase.setUp>` instead of ``__init__``.
|
|
||||||
|
|
||||||
If you run into this issue using ``tornado.AsyncTestCase``, please see `issue 12263 <https://github.com/pytest-dev/pytest/issues/12263>`_.
|
|
||||||
|
|
||||||
If you run into this issue using an abstract ``TestCase`` subclass, please see `issue 12275 <https://github.com/pytest-dev/pytest/issues/12275>`_.
|
|
||||||
|
|
||||||
Historical note: the effect of this change on custom TestCase implementations was not properly considered initially, this is why it was done in a minor release. We apologize for the inconvenience.
|
|
||||||
|
|
||||||
Deprecations
|
Deprecations
|
||||||
------------
|
------------
|
||||||
|
|
||||||
|
|
@ -232,7 +150,7 @@ Improvements
|
||||||
- `#11311 <https://github.com/pytest-dev/pytest/issues/11311>`_: When using ``--override-ini`` for paths in invocations without a configuration file defined, the current working directory is used
|
- `#11311 <https://github.com/pytest-dev/pytest/issues/11311>`_: When using ``--override-ini`` for paths in invocations without a configuration file defined, the current working directory is used
|
||||||
as the relative directory.
|
as the relative directory.
|
||||||
|
|
||||||
Previously this would raise an :class:`AssertionError`.
|
Previoulsy this would raise an :class:`AssertionError`.
|
||||||
|
|
||||||
|
|
||||||
- `#11475 <https://github.com/pytest-dev/pytest/issues/11475>`_: :ref:`--import-mode=importlib <import-mode-importlib>` now tries to import modules using the standard import mechanism (but still without changing :py:data:`sys.path`), falling back to importing modules directly only if that fails.
|
- `#11475 <https://github.com/pytest-dev/pytest/issues/11475>`_: :ref:`--import-mode=importlib <import-mode-importlib>` now tries to import modules using the standard import mechanism (but still without changing :py:data:`sys.path`), falling back to importing modules directly only if that fails.
|
||||||
|
|
@ -268,7 +186,7 @@ Bug Fixes
|
||||||
|
|
||||||
- `#11904 <https://github.com/pytest-dev/pytest/issues/11904>`_: Fixed a regression in pytest 8.0.0 that would cause test collection to fail due to permission errors when using ``--pyargs``.
|
- `#11904 <https://github.com/pytest-dev/pytest/issues/11904>`_: Fixed a regression in pytest 8.0.0 that would cause test collection to fail due to permission errors when using ``--pyargs``.
|
||||||
|
|
||||||
This change improves the collection tree for tests specified using ``--pyargs``, see :pr:`12043` for a comparison with pytest 8.0 and <8.
|
This change improves the collection tree for tests specified using ``--pyargs``, see :pull:`12043` for a comparison with pytest 8.0 and <8.
|
||||||
|
|
||||||
|
|
||||||
- `#12011 <https://github.com/pytest-dev/pytest/issues/12011>`_: Fixed a regression in 8.0.1 whereby ``setup_module`` xunit-style fixtures are not executed when ``--doctest-modules`` is passed.
|
- `#12011 <https://github.com/pytest-dev/pytest/issues/12011>`_: Fixed a regression in 8.0.1 whereby ``setup_module`` xunit-style fixtures are not executed when ``--doctest-modules`` is passed.
|
||||||
|
|
@ -1422,7 +1340,7 @@ Bug Fixes
|
||||||
tests/link -> tests/real
|
tests/link -> tests/real
|
||||||
|
|
||||||
running ``pytest tests`` now imports the conftest twice, once as ``tests/real/conftest.py`` and once as ``tests/link/conftest.py``.
|
running ``pytest tests`` now imports the conftest twice, once as ``tests/real/conftest.py`` and once as ``tests/link/conftest.py``.
|
||||||
This is a fix to match a similar change made to test collection itself in pytest 6.0 (see :pr:`6523` for details).
|
This is a fix to match a similar change made to test collection itself in pytest 6.0 (see :pull:`6523` for details).
|
||||||
|
|
||||||
|
|
||||||
- `#9626 <https://github.com/pytest-dev/pytest/issues/9626>`_: Fixed count of selected tests on terminal collection summary when there were errors or skipped modules.
|
- `#9626 <https://github.com/pytest-dev/pytest/issues/9626>`_: Fixed count of selected tests on terminal collection summary when there were errors or skipped modules.
|
||||||
|
|
@ -1475,7 +1393,7 @@ Deprecations
|
||||||
``__init__`` method, they should take ``**kwargs``. See
|
``__init__`` method, they should take ``**kwargs``. See
|
||||||
:ref:`uncooperative-constructors-deprecated` for details.
|
:ref:`uncooperative-constructors-deprecated` for details.
|
||||||
|
|
||||||
Note that a deprecation warning is only emitted when there is a conflict in the
|
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
|
arguments pytest expected to pass. This deprecation was already part of pytest
|
||||||
7.0.0rc1 but wasn't documented.
|
7.0.0rc1 but wasn't documented.
|
||||||
|
|
||||||
|
|
@ -1517,7 +1435,7 @@ Breaking Changes
|
||||||
- `#7259 <https://github.com/pytest-dev/pytest/issues/7259>`_: The :ref:`Node.reportinfo() <non-python tests>` function first return value type has been expanded from `py.path.local | str` to `os.PathLike[str] | str`.
|
- `#7259 <https://github.com/pytest-dev/pytest/issues/7259>`_: The :ref:`Node.reportinfo() <non-python tests>` function first return value type has been expanded from `py.path.local | str` to `os.PathLike[str] | str`.
|
||||||
|
|
||||||
Most plugins which refer to `reportinfo()` only define it as part of a custom :class:`pytest.Item` implementation.
|
Most plugins which refer to `reportinfo()` only define it as part of a custom :class:`pytest.Item` implementation.
|
||||||
Since `py.path.local` is an `os.PathLike[str]`, these plugins are unaffected.
|
Since `py.path.local` is an `os.PathLike[str]`, these plugins are unaffacted.
|
||||||
|
|
||||||
Plugins and users which call `reportinfo()`, use the first return value and interact with it as a `py.path.local`, would need to adjust by calling `py.path.local(fspath)`.
|
Plugins and users which call `reportinfo()`, use the first return value and interact with it as a `py.path.local`, would need to adjust by calling `py.path.local(fspath)`.
|
||||||
Although preferably, avoid the legacy `py.path.local` and use `pathlib.Path`, or use `item.location` or `item.path`, instead.
|
Although preferably, avoid the legacy `py.path.local` and use `pathlib.Path`, or use `item.location` or `item.path`, instead.
|
||||||
|
|
@ -2025,7 +1943,7 @@ Bug Fixes
|
||||||
the ``tmp_path``/``tmpdir`` fixture). Now the directories are created with
|
the ``tmp_path``/``tmpdir`` fixture). Now the directories are created with
|
||||||
private permissions.
|
private permissions.
|
||||||
|
|
||||||
pytest used to silently use a preexisting ``/tmp/pytest-of-<username>`` directory,
|
pytest used to silently use a pre-existing ``/tmp/pytest-of-<username>`` directory,
|
||||||
even if owned by another user. This means another user could pre-create such a
|
even if owned by another user. This means another user could pre-create such a
|
||||||
directory and gain control of another user's temporary directory. Now such a
|
directory and gain control of another user's temporary directory. Now such a
|
||||||
condition results in an error.
|
condition results in an error.
|
||||||
|
|
@ -2591,7 +2509,7 @@ Breaking Changes
|
||||||
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.
|
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
|
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
|
||||||
:pr:`6523` for details).
|
:pull:`6523` for details).
|
||||||
|
|
||||||
This might break test suites which made use of this feature; the fix is to create a symlink
|
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.
|
for the entire test tree, and not only to partial files/tress as it was possible previously.
|
||||||
|
|
@ -2752,7 +2670,7 @@ Features
|
||||||
also changes ``sys.modules`` as a side-effect), which works but has a number of drawbacks, like requiring test modules
|
also changes ``sys.modules`` as a side-effect), which works but has a number of drawbacks, like requiring test modules
|
||||||
that don't live in packages to have unique names (as they need to reside under a unique name in ``sys.modules``).
|
that don't live in packages to have unique names (as they need to reside under a unique name in ``sys.modules``).
|
||||||
|
|
||||||
``--import-mode=importlib`` uses more fine-grained import mechanisms from ``importlib`` which don't
|
``--import-mode=importlib`` uses more fine grained import mechanisms from ``importlib`` which don't
|
||||||
require pytest to change ``sys.path`` or ``sys.modules`` at all, eliminating much of the drawbacks
|
require pytest to change ``sys.path`` or ``sys.modules`` at all, eliminating much of the drawbacks
|
||||||
of the previous mode.
|
of the previous mode.
|
||||||
|
|
||||||
|
|
@ -2769,7 +2687,7 @@ Improvements
|
||||||
------------
|
------------
|
||||||
|
|
||||||
- :issue:`4375`: The ``pytest`` command now suppresses the ``BrokenPipeError`` error message that
|
- :issue:`4375`: The ``pytest`` command now suppresses the ``BrokenPipeError`` error message that
|
||||||
is printed to stderr when the output of ``pytest`` is piped and the pipe is
|
is printed to stderr when the output of ``pytest`` is piped and and the pipe is
|
||||||
closed by the piped-to program (common examples are ``less`` and ``head``).
|
closed by the piped-to program (common examples are ``less`` and ``head``).
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -2874,7 +2792,7 @@ Bug Fixes
|
||||||
- :issue:`6871`: Fix crash with captured output when using :fixture:`capsysbinary`.
|
- :issue:`6871`: Fix crash with captured output when using :fixture:`capsysbinary`.
|
||||||
|
|
||||||
|
|
||||||
- :issue:`6909`: Revert the change introduced by :pr:`6330`, which required all arguments to ``@pytest.mark.parametrize`` to be explicitly defined in the function signature.
|
- :issue:`6909`: Revert the change introduced by :pull:`6330`, which required all arguments to ``@pytest.mark.parametrize`` to 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.
|
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.
|
||||||
|
|
||||||
|
|
@ -3044,7 +2962,7 @@ pytest 5.4.1 (2020-03-13)
|
||||||
Bug Fixes
|
Bug Fixes
|
||||||
---------
|
---------
|
||||||
|
|
||||||
- :issue:`6909`: Revert the change introduced by :pr:`6330`, which required all arguments to ``@pytest.mark.parametrize`` to be explicitly defined in the function signature.
|
- :issue:`6909`: Revert the change introduced by :pull:`6330`, which required all arguments to ``@pytest.mark.parametrize`` to 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.
|
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.
|
||||||
|
|
||||||
|
|
@ -3071,7 +2989,7 @@ Breaking Changes
|
||||||
This hook has been marked as deprecated and not been even called by pytest for over 10 years now.
|
This hook has been marked as deprecated and not been even called by pytest for over 10 years now.
|
||||||
|
|
||||||
|
|
||||||
- :issue:`6673`: Reversed / fix meaning of "+/-" in error diffs. "-" means that something expected is missing in the result and "+" means that there are unexpected extras in the result.
|
- :issue:`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.
|
||||||
|
|
||||||
|
|
||||||
- :issue:`6737`: The ``cached_result`` attribute of ``FixtureDef`` is now set to ``None`` when
|
- :issue:`6737`: The ``cached_result`` attribute of ``FixtureDef`` is now set to ``None`` when
|
||||||
|
|
@ -3360,9 +3278,7 @@ Bug Fixes
|
||||||
- :issue:`5914`: pytester: fix :py:func:`~pytest.LineMatcher.no_fnmatch_line` when used after positive matching.
|
- :issue:`5914`: pytester: fix :py:func:`~pytest.LineMatcher.no_fnmatch_line` when used after positive matching.
|
||||||
|
|
||||||
|
|
||||||
- :issue:`6082`: Fix line detection for doctest samples inside
|
- :issue:`6082`: Fix line detection for doctest samples inside :py:class:`python:property` docstrings, as a workaround to :bpo:`17446`.
|
||||||
:py:class:`python:property` docstrings, as a workaround to
|
|
||||||
:issue:`python/cpython#61648`.
|
|
||||||
|
|
||||||
|
|
||||||
- :issue:`6254`: Fix compatibility with pytest-parallel (regression in pytest 5.3.0).
|
- :issue:`6254`: Fix compatibility with pytest-parallel (regression in pytest 5.3.0).
|
||||||
|
|
@ -4069,7 +3985,7 @@ Bug Fixes
|
||||||
(``--collect-only``) when ``--log-cli-level`` is used.
|
(``--collect-only``) when ``--log-cli-level`` is used.
|
||||||
|
|
||||||
|
|
||||||
- :issue:`5389`: Fix regressions of :pr:`5063` for ``importlib_metadata.PathDistribution`` which have their ``files`` attribute being ``None``.
|
- :issue:`5389`: Fix regressions of :pull:`5063` for ``importlib_metadata.PathDistribution`` which have their ``files`` attribute being ``None``.
|
||||||
|
|
||||||
|
|
||||||
- :issue:`5390`: Fix regression where the ``obj`` attribute of ``TestCase`` items was no longer bound to methods.
|
- :issue:`5390`: Fix regression where the ``obj`` attribute of ``TestCase`` items was no longer bound to methods.
|
||||||
|
|
@ -4270,7 +4186,7 @@ Bug Fixes
|
||||||
(``--collect-only``) when ``--log-cli-level`` is used.
|
(``--collect-only``) when ``--log-cli-level`` is used.
|
||||||
|
|
||||||
|
|
||||||
- :issue:`5389`: Fix regressions of :pr:`5063` for ``importlib_metadata.PathDistribution`` which have their ``files`` attribute being ``None``.
|
- :issue:`5389`: Fix regressions of :pull:`5063` for ``importlib_metadata.PathDistribution`` which have their ``files`` attribute being ``None``.
|
||||||
|
|
||||||
|
|
||||||
- :issue:`5390`: Fix regression where the ``obj`` attribute of ``TestCase`` items was no longer bound to methods.
|
- :issue:`5390`: Fix regression where the ``obj`` attribute of ``TestCase`` items was no longer bound to methods.
|
||||||
|
|
@ -4678,7 +4594,7 @@ Bug Fixes
|
||||||
Improved Documentation
|
Improved Documentation
|
||||||
----------------------
|
----------------------
|
||||||
|
|
||||||
- :issue:`4974`: Update docs for ``pytest_cmdline_parse`` hook to note availability limitations
|
- :issue:`4974`: Update docs for ``pytest_cmdline_parse`` hook to note availability liminations
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -6536,7 +6452,7 @@ Features
|
||||||
Bug Fixes
|
Bug Fixes
|
||||||
---------
|
---------
|
||||||
|
|
||||||
- Fix hanging pexpect test on macOS by using flush() instead of wait().
|
- Fix hanging pexpect test on MacOS by using flush() instead of wait().
|
||||||
(:issue:`2022`)
|
(:issue:`2022`)
|
||||||
|
|
||||||
- Fix restoring Python state after in-process pytest runs with the
|
- Fix restoring Python state after in-process pytest runs with the
|
||||||
|
|
@ -6584,7 +6500,7 @@ Trivial/Internal Changes
|
||||||
------------------------
|
------------------------
|
||||||
|
|
||||||
- Show a simple and easy error when keyword expressions trigger a syntax error
|
- Show a simple and easy error when keyword expressions trigger a syntax error
|
||||||
(for example, ``"-k foo and import"`` will show an error that you cannot use
|
(for example, ``"-k foo and import"`` will show an error that you can not use
|
||||||
the ``import`` keyword in expressions). (:issue:`2953`)
|
the ``import`` keyword in expressions). (:issue:`2953`)
|
||||||
|
|
||||||
- Change parametrized automatic test id generation to use the ``__name__``
|
- Change parametrized automatic test id generation to use the ``__name__``
|
||||||
|
|
@ -7231,10 +7147,10 @@ New Features
|
||||||
* Added ``junit_suite_name`` ini option to specify root ``<testsuite>`` name for JUnit XML reports (:issue:`533`).
|
* Added ``junit_suite_name`` ini option to specify root ``<testsuite>`` name for JUnit XML reports (:issue:`533`).
|
||||||
|
|
||||||
* Added an ini option ``doctest_encoding`` to specify which encoding to use for doctest files.
|
* Added an ini option ``doctest_encoding`` to specify which encoding to use for doctest files.
|
||||||
Thanks :user:`wheerd` for the PR (:pr:`2101`).
|
Thanks :user:`wheerd` for the PR (:pull:`2101`).
|
||||||
|
|
||||||
* ``pytest.warns`` now checks for subclass relationship rather than
|
* ``pytest.warns`` now checks for subclass relationship rather than
|
||||||
class equality. Thanks :user:`lesteve` for the PR (:pr:`2166`)
|
class equality. Thanks :user:`lesteve` for the PR (:pull:`2166`)
|
||||||
|
|
||||||
* ``pytest.raises`` now asserts that the error message matches a text or regex
|
* ``pytest.raises`` now asserts that the error message matches a text or regex
|
||||||
with the ``match`` keyword argument. Thanks :user:`Kriechi` for the PR.
|
with the ``match`` keyword argument. Thanks :user:`Kriechi` for the PR.
|
||||||
|
|
@ -7262,7 +7178,7 @@ Changes
|
||||||
the failure. (:issue:`2228`) Thanks to :user:`kkoukiou` for the PR.
|
the failure. (:issue:`2228`) Thanks to :user:`kkoukiou` for the PR.
|
||||||
|
|
||||||
* Testcase reports with a ``url`` attribute will now properly write this to junitxml.
|
* Testcase reports with a ``url`` attribute will now properly write this to junitxml.
|
||||||
Thanks :user:`fushi` for the PR (:pr:`1874`).
|
Thanks :user:`fushi` for the PR (:pull:`1874`).
|
||||||
|
|
||||||
* Remove common items from dict comparison output when verbosity=1. Also update
|
* Remove common items from dict comparison output when verbosity=1. Also update
|
||||||
the truncation message to make it clearer that pytest truncates all
|
the truncation message to make it clearer that pytest truncates all
|
||||||
|
|
@ -7271,7 +7187,7 @@ Changes
|
||||||
|
|
||||||
* ``--pdbcls`` no longer implies ``--pdb``. This makes it possible to use
|
* ``--pdbcls`` no longer implies ``--pdb``. This makes it possible to use
|
||||||
``addopts=--pdbcls=module.SomeClass`` on ``pytest.ini``. Thanks :user:`davidszotten` for
|
``addopts=--pdbcls=module.SomeClass`` on ``pytest.ini``. Thanks :user:`davidszotten` for
|
||||||
the PR (:pr:`1952`).
|
the PR (:pull:`1952`).
|
||||||
|
|
||||||
* fix :issue:`2013`: turn RecordedWarning into ``namedtuple``,
|
* fix :issue:`2013`: turn RecordedWarning into ``namedtuple``,
|
||||||
to give it a comprehensible repr while preventing unwarranted modification.
|
to give it a comprehensible repr while preventing unwarranted modification.
|
||||||
|
|
@ -7525,7 +7441,7 @@ Bug Fixes
|
||||||
a sequence of strings) when modules are considered for assertion rewriting.
|
a sequence of strings) when modules are considered for assertion rewriting.
|
||||||
Due to this bug, much more modules were being rewritten than necessary
|
Due to this bug, much more modules were being rewritten than necessary
|
||||||
if a test suite uses ``pytest_plugins`` to load internal plugins (:issue:`1888`).
|
if a test suite uses ``pytest_plugins`` to load internal plugins (:issue:`1888`).
|
||||||
Thanks :user:`jaraco` for the report and :user:`nicoddemus` for the PR (:pr:`1891`).
|
Thanks :user:`jaraco` for the report and :user:`nicoddemus` for the PR (:pull:`1891`).
|
||||||
|
|
||||||
* Do not call tearDown and cleanups when running tests from
|
* Do not call tearDown and cleanups when running tests from
|
||||||
``unittest.TestCase`` subclasses with ``--pdb``
|
``unittest.TestCase`` subclasses with ``--pdb``
|
||||||
|
|
@ -7580,12 +7496,12 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
* ``--nomagic``: use ``--assert=plain`` instead;
|
* ``--nomagic``: use ``--assert=plain`` instead;
|
||||||
* ``--report``: use ``-r`` instead;
|
* ``--report``: use ``-r`` instead;
|
||||||
|
|
||||||
Thanks to :user:`RedBeardCode` for the PR (:pr:`1664`).
|
Thanks to :user:`RedBeardCode` for the PR (:pull:`1664`).
|
||||||
|
|
||||||
* ImportErrors in plugins now are a fatal error instead of issuing a
|
* ImportErrors in plugins now are a fatal error instead of issuing a
|
||||||
pytest warning (:issue:`1479`). Thanks to :user:`The-Compiler` for the PR.
|
pytest warning (:issue:`1479`). Thanks to :user:`The-Compiler` for the PR.
|
||||||
|
|
||||||
* Removed support code for Python 3 versions < 3.3 (:pr:`1627`).
|
* Removed support code for Python 3 versions < 3.3 (:pull:`1627`).
|
||||||
|
|
||||||
* Removed all ``py.test-X*`` entry points. The versioned, suffixed entry points
|
* Removed all ``py.test-X*`` entry points. The versioned, suffixed entry points
|
||||||
were never documented and a leftover from a pre-virtualenv era. These entry
|
were never documented and a leftover from a pre-virtualenv era. These entry
|
||||||
|
|
@ -7596,19 +7512,19 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
* ``pytest.skip()`` now raises an error when used to decorate a test function,
|
* ``pytest.skip()`` now raises an error when used to decorate a test function,
|
||||||
as opposed to its original intent (to imperatively skip a test inside a test function). Previously
|
as opposed to its original intent (to imperatively skip a test inside a test function). Previously
|
||||||
this usage would cause the entire module to be skipped (:issue:`607`).
|
this usage would cause the entire module to be skipped (:issue:`607`).
|
||||||
Thanks :user:`omarkohl` for the complete PR (:pr:`1519`).
|
Thanks :user:`omarkohl` for the complete PR (:pull:`1519`).
|
||||||
|
|
||||||
* Exit tests if a collection error occurs. A poll indicated most users will hit CTRL-C
|
* Exit tests if a collection error occurs. A poll indicated most users will hit CTRL-C
|
||||||
anyway as soon as they see collection errors, so pytest might as well make that the default behavior (:issue:`1421`).
|
anyway as soon as they see collection errors, so pytest might as well make that the default behavior (:issue:`1421`).
|
||||||
A ``--continue-on-collection-errors`` option has been added to restore the previous behaviour.
|
A ``--continue-on-collection-errors`` option has been added to restore the previous behaviour.
|
||||||
Thanks :user:`olegpidsadnyi` and :user:`omarkohl` for the complete PR (:pr:`1628`).
|
Thanks :user:`olegpidsadnyi` and :user:`omarkohl` for the complete PR (:pull:`1628`).
|
||||||
|
|
||||||
* Renamed the pytest ``pdb`` module (plugin) into ``debugging`` to avoid clashes with the builtin ``pdb`` module.
|
* Renamed the pytest ``pdb`` module (plugin) into ``debugging`` to avoid clashes with the builtin ``pdb`` module.
|
||||||
|
|
||||||
* Raise a helpful failure message when requesting a parametrized fixture at runtime,
|
* Raise a helpful failure message when requesting a parametrized fixture at runtime,
|
||||||
e.g. with ``request.getfixturevalue``. Previously these parameters were simply
|
e.g. with ``request.getfixturevalue``. Previously these parameters were simply
|
||||||
never defined, so a fixture decorated like ``@pytest.fixture(params=[0, 1, 2])``
|
never defined, so a fixture decorated like ``@pytest.fixture(params=[0, 1, 2])``
|
||||||
only ran once (:pr:`460`).
|
only ran once (:pull:`460`).
|
||||||
Thanks to :user:`nikratio` for the bug report, :user:`RedBeardCode` and :user:`tomviner` for the PR.
|
Thanks to :user:`nikratio` for the bug report, :user:`RedBeardCode` and :user:`tomviner` for the PR.
|
||||||
|
|
||||||
* ``_pytest.monkeypatch.monkeypatch`` class has been renamed to ``_pytest.monkeypatch.MonkeyPatch``
|
* ``_pytest.monkeypatch.monkeypatch`` class has been renamed to ``_pytest.monkeypatch.MonkeyPatch``
|
||||||
|
|
@ -7626,7 +7542,7 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
|
|
||||||
* New ``doctest_namespace`` fixture for injecting names into the
|
* New ``doctest_namespace`` fixture for injecting names into the
|
||||||
namespace in which doctests run.
|
namespace in which doctests run.
|
||||||
Thanks :user:`milliams` for the complete PR (:pr:`1428`).
|
Thanks :user:`milliams` for the complete PR (:pull:`1428`).
|
||||||
|
|
||||||
* New ``--doctest-report`` option available to change the output format of diffs
|
* New ``--doctest-report`` option available to change the output format of diffs
|
||||||
when running (failing) doctests (implements :issue:`1749`).
|
when running (failing) doctests (implements :issue:`1749`).
|
||||||
|
|
@ -7634,23 +7550,23 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
|
|
||||||
* New ``name`` argument to ``pytest.fixture`` decorator which allows a custom name
|
* New ``name`` argument to ``pytest.fixture`` decorator which allows a custom name
|
||||||
for a fixture (to solve the funcarg-shadowing-fixture problem).
|
for a fixture (to solve the funcarg-shadowing-fixture problem).
|
||||||
Thanks :user:`novas0x2a` for the complete PR (:pr:`1444`).
|
Thanks :user:`novas0x2a` for the complete PR (:pull:`1444`).
|
||||||
|
|
||||||
* New ``approx()`` function for easily comparing floating-point numbers in
|
* New ``approx()`` function for easily comparing floating-point numbers in
|
||||||
tests.
|
tests.
|
||||||
Thanks :user:`kalekundert` for the complete PR (:pr:`1441`).
|
Thanks :user:`kalekundert` for the complete PR (:pull:`1441`).
|
||||||
|
|
||||||
* Ability to add global properties in the final xunit output file by accessing
|
* Ability to add global properties in the final xunit output file by accessing
|
||||||
the internal ``junitxml`` plugin (experimental).
|
the internal ``junitxml`` plugin (experimental).
|
||||||
Thanks :user:`tareqalayan` for the complete PR :pr:`1454`).
|
Thanks :user:`tareqalayan` for the complete PR :pull:`1454`).
|
||||||
|
|
||||||
* New ``ExceptionInfo.match()`` method to match a regular expression on the
|
* New ``ExceptionInfo.match()`` method to match a regular expression on the
|
||||||
string representation of an exception (:issue:`372`).
|
string representation of an exception (:issue:`372`).
|
||||||
Thanks :user:`omarkohl` for the complete PR (:pr:`1502`).
|
Thanks :user:`omarkohl` for the complete PR (:pull:`1502`).
|
||||||
|
|
||||||
* ``__tracebackhide__`` can now also be set to a callable which then can decide
|
* ``__tracebackhide__`` can now also be set to a callable which then can decide
|
||||||
whether to filter the traceback based on the ``ExceptionInfo`` object passed
|
whether to filter the traceback based on the ``ExceptionInfo`` object passed
|
||||||
to it. Thanks :user:`The-Compiler` for the complete PR (:pr:`1526`).
|
to it. Thanks :user:`The-Compiler` for the complete PR (:pull:`1526`).
|
||||||
|
|
||||||
* New ``pytest_make_parametrize_id(config, val)`` hook which can be used by plugins to provide
|
* New ``pytest_make_parametrize_id(config, val)`` hook which can be used by plugins to provide
|
||||||
friendly strings for custom types.
|
friendly strings for custom types.
|
||||||
|
|
@ -7668,7 +7584,7 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
* Introduce ``pytest`` command as recommended entry point. Note that ``py.test``
|
* Introduce ``pytest`` command as recommended entry point. Note that ``py.test``
|
||||||
still works and is not scheduled for removal. Closes proposal
|
still works and is not scheduled for removal. Closes proposal
|
||||||
:issue:`1629`. Thanks :user:`obestwalter` and :user:`davehunt` for the complete PR
|
:issue:`1629`. Thanks :user:`obestwalter` and :user:`davehunt` for the complete PR
|
||||||
(:pr:`1633`).
|
(:pull:`1633`).
|
||||||
|
|
||||||
* New cli flags:
|
* New cli flags:
|
||||||
|
|
||||||
|
|
@ -7712,19 +7628,19 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
|
|
||||||
* Change ``report.outcome`` for ``xpassed`` tests to ``"passed"`` in non-strict
|
* Change ``report.outcome`` for ``xpassed`` tests to ``"passed"`` in non-strict
|
||||||
mode and ``"failed"`` in strict mode. Thanks to :user:`hackebrot` for the PR
|
mode and ``"failed"`` in strict mode. Thanks to :user:`hackebrot` for the PR
|
||||||
(:pr:`1795`) and :user:`gprasad84` for report (:issue:`1546`).
|
(:pull:`1795`) and :user:`gprasad84` for report (:issue:`1546`).
|
||||||
|
|
||||||
* Tests marked with ``xfail(strict=False)`` (the default) now appear in
|
* Tests marked with ``xfail(strict=False)`` (the default) now appear in
|
||||||
JUnitXML reports as passing tests instead of skipped.
|
JUnitXML reports as passing tests instead of skipped.
|
||||||
Thanks to :user:`hackebrot` for the PR (:pr:`1795`).
|
Thanks to :user:`hackebrot` for the PR (:pull:`1795`).
|
||||||
|
|
||||||
* Highlight path of the file location in the error report to make it easier to copy/paste.
|
* Highlight path of the file location in the error report to make it easier to copy/paste.
|
||||||
Thanks :user:`suzaku` for the PR (:pr:`1778`).
|
Thanks :user:`suzaku` for the PR (:pull:`1778`).
|
||||||
|
|
||||||
* Fixtures marked with ``@pytest.fixture`` can now use ``yield`` statements exactly like
|
* Fixtures marked with ``@pytest.fixture`` can now use ``yield`` statements exactly like
|
||||||
those marked with the ``@pytest.yield_fixture`` decorator. This change renders
|
those marked with the ``@pytest.yield_fixture`` decorator. This change renders
|
||||||
``@pytest.yield_fixture`` deprecated and makes ``@pytest.fixture`` with ``yield`` statements
|
``@pytest.yield_fixture`` deprecated and makes ``@pytest.fixture`` with ``yield`` statements
|
||||||
the preferred way to write teardown code (:pr:`1461`).
|
the preferred way to write teardown code (:pull:`1461`).
|
||||||
Thanks :user:`csaftoiu` for bringing this to attention and :user:`nicoddemus` for the PR.
|
Thanks :user:`csaftoiu` for bringing this to attention and :user:`nicoddemus` for the PR.
|
||||||
|
|
||||||
* Explicitly passed parametrize ids do not get escaped to ascii (:issue:`1351`).
|
* Explicitly passed parametrize ids do not get escaped to ascii (:issue:`1351`).
|
||||||
|
|
@ -7735,11 +7651,11 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
Thanks :user:`nicoddemus` for the PR.
|
Thanks :user:`nicoddemus` for the PR.
|
||||||
|
|
||||||
* ``pytest_terminal_summary`` hook now receives the ``exitstatus``
|
* ``pytest_terminal_summary`` hook now receives the ``exitstatus``
|
||||||
of the test session as argument. Thanks :user:`blueyed` for the PR (:pr:`1809`).
|
of the test session as argument. Thanks :user:`blueyed` for the PR (:pull:`1809`).
|
||||||
|
|
||||||
* Parametrize ids can accept ``None`` as specific test id, in which case the
|
* Parametrize ids can accept ``None`` as specific test id, in which case the
|
||||||
automatically generated id for that argument will be used.
|
automatically generated id for that argument will be used.
|
||||||
Thanks :user:`palaviv` for the complete PR (:pr:`1468`).
|
Thanks :user:`palaviv` for the complete PR (:pull:`1468`).
|
||||||
|
|
||||||
* The parameter to xunit-style setup/teardown methods (``setup_method``,
|
* The parameter to xunit-style setup/teardown methods (``setup_method``,
|
||||||
``setup_module``, etc.) is now optional and may be omitted.
|
``setup_module``, etc.) is now optional and may be omitted.
|
||||||
|
|
@ -7747,32 +7663,32 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
|
|
||||||
* Improved automatic id generation selection in case of duplicate ids in
|
* Improved automatic id generation selection in case of duplicate ids in
|
||||||
parametrize.
|
parametrize.
|
||||||
Thanks :user:`palaviv` for the complete PR (:pr:`1474`).
|
Thanks :user:`palaviv` for the complete PR (:pull:`1474`).
|
||||||
|
|
||||||
* Now pytest warnings summary is shown up by default. Added a new flag
|
* Now pytest warnings summary is shown up by default. Added a new flag
|
||||||
``--disable-pytest-warnings`` to explicitly disable the warnings summary (:issue:`1668`).
|
``--disable-pytest-warnings`` to explicitly disable the warnings summary (:issue:`1668`).
|
||||||
|
|
||||||
* Make ImportError during collection more explicit by reminding
|
* Make ImportError during collection more explicit by reminding
|
||||||
the user to check the name of the test module/package(s) (:issue:`1426`).
|
the user to check the name of the test module/package(s) (:issue:`1426`).
|
||||||
Thanks :user:`omarkohl` for the complete PR (:pr:`1520`).
|
Thanks :user:`omarkohl` for the complete PR (:pull:`1520`).
|
||||||
|
|
||||||
* Add ``build/`` and ``dist/`` to the default ``--norecursedirs`` list. Thanks
|
* Add ``build/`` and ``dist/`` to the default ``--norecursedirs`` list. Thanks
|
||||||
:user:`mikofski` for the report and :user:`tomviner` for the PR (:issue:`1544`).
|
:user:`mikofski` for the report and :user:`tomviner` for the PR (:issue:`1544`).
|
||||||
|
|
||||||
* ``pytest.raises`` in the context manager form accepts a custom
|
* ``pytest.raises`` in the context manager form accepts a custom
|
||||||
``message`` to raise when no exception occurred.
|
``message`` to raise when no exception occurred.
|
||||||
Thanks :user:`palaviv` for the complete PR (:pr:`1616`).
|
Thanks :user:`palaviv` for the complete PR (:pull:`1616`).
|
||||||
|
|
||||||
* ``conftest.py`` files now benefit from assertion rewriting; previously it
|
* ``conftest.py`` files now benefit from assertion rewriting; previously it
|
||||||
was only available for test modules. Thanks :user:`flub`, :user:`sober7` and
|
was only available for test modules. Thanks :user:`flub`, :user:`sober7` and
|
||||||
:user:`nicoddemus` for the PR (:issue:`1619`).
|
:user:`nicoddemus` for the PR (:issue:`1619`).
|
||||||
|
|
||||||
* Text documents without any doctests no longer appear as "skipped".
|
* Text documents without any doctests no longer appear as "skipped".
|
||||||
Thanks :user:`graingert` for reporting and providing a full PR (:pr:`1580`).
|
Thanks :user:`graingert` for reporting and providing a full PR (:pull:`1580`).
|
||||||
|
|
||||||
* Ensure that a module within a namespace package can be found when it
|
* Ensure that a module within a namespace package can be found when it
|
||||||
is specified on the command line together with the ``--pyargs``
|
is specified on the command line together with the ``--pyargs``
|
||||||
option. Thanks to :user:`taschini` for the PR (:pr:`1597`).
|
option. Thanks to :user:`taschini` for the PR (:pull:`1597`).
|
||||||
|
|
||||||
* Always include full assertion explanation during assertion rewriting. The previous behaviour was hiding
|
* Always include full assertion explanation during assertion rewriting. The previous behaviour was hiding
|
||||||
sub-expressions that happened to be ``False``, assuming this was redundant information.
|
sub-expressions that happened to be ``False``, assuming this was redundant information.
|
||||||
|
|
@ -7788,20 +7704,20 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
Thanks :user:`nicoddemus` for the PR.
|
Thanks :user:`nicoddemus` for the PR.
|
||||||
|
|
||||||
* ``[pytest]`` sections in ``setup.cfg`` files should now be named ``[tool:pytest]``
|
* ``[pytest]`` sections in ``setup.cfg`` files should now be named ``[tool:pytest]``
|
||||||
to avoid conflicts with other distutils commands (see :pr:`567`). ``[pytest]`` sections in
|
to avoid conflicts with other distutils commands (see :pull:`567`). ``[pytest]`` sections in
|
||||||
``pytest.ini`` or ``tox.ini`` files are supported and unchanged.
|
``pytest.ini`` or ``tox.ini`` files are supported and unchanged.
|
||||||
Thanks :user:`nicoddemus` for the PR.
|
Thanks :user:`nicoddemus` for the PR.
|
||||||
|
|
||||||
* Using ``pytest_funcarg__`` prefix to declare fixtures is considered deprecated and will be
|
* Using ``pytest_funcarg__`` prefix to declare fixtures is considered deprecated and will be
|
||||||
removed in pytest-4.0 (:pr:`1684`).
|
removed in pytest-4.0 (:pull:`1684`).
|
||||||
Thanks :user:`nicoddemus` for the PR.
|
Thanks :user:`nicoddemus` for the PR.
|
||||||
|
|
||||||
* Passing a command-line string to ``pytest.main()`` is considered deprecated and scheduled
|
* Passing a command-line string to ``pytest.main()`` is considered deprecated and scheduled
|
||||||
for removal in pytest-4.0. It is recommended to pass a list of arguments instead (:pr:`1723`).
|
for removal in pytest-4.0. It is recommended to pass a list of arguments instead (:pull:`1723`).
|
||||||
|
|
||||||
* Rename ``getfuncargvalue`` to ``getfixturevalue``. ``getfuncargvalue`` is
|
* Rename ``getfuncargvalue`` to ``getfixturevalue``. ``getfuncargvalue`` is
|
||||||
still present but is now considered deprecated. Thanks to :user:`RedBeardCode` and :user:`tomviner`
|
still present but is now considered deprecated. Thanks to :user:`RedBeardCode` and :user:`tomviner`
|
||||||
for the PR (:pr:`1626`).
|
for the PR (:pull:`1626`).
|
||||||
|
|
||||||
* ``optparse`` type usage now triggers DeprecationWarnings (:issue:`1740`).
|
* ``optparse`` type usage now triggers DeprecationWarnings (:issue:`1740`).
|
||||||
|
|
||||||
|
|
@ -7859,11 +7775,11 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
:user:`tomviner` for the PR.
|
:user:`tomviner` for the PR.
|
||||||
|
|
||||||
* ``ConftestImportFailure`` now shows the traceback making it easier to
|
* ``ConftestImportFailure`` now shows the traceback making it easier to
|
||||||
identify bugs in ``conftest.py`` files (:pr:`1516`). Thanks :user:`txomon` for
|
identify bugs in ``conftest.py`` files (:pull:`1516`). Thanks :user:`txomon` for
|
||||||
the PR.
|
the PR.
|
||||||
|
|
||||||
* Text documents without any doctests no longer appear as "skipped".
|
* Text documents without any doctests no longer appear as "skipped".
|
||||||
Thanks :user:`graingert` for reporting and providing a full PR (:pr:`1580`).
|
Thanks :user:`graingert` for reporting and providing a full PR (:pull:`1580`).
|
||||||
|
|
||||||
* Fixed collection of classes with custom ``__new__`` method.
|
* Fixed collection of classes with custom ``__new__`` method.
|
||||||
Fixes :issue:`1579`. Thanks to :user:`Stranger6667` for the PR.
|
Fixes :issue:`1579`. Thanks to :user:`Stranger6667` for the PR.
|
||||||
|
|
@ -7871,7 +7787,7 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
* Fixed scope overriding inside metafunc.parametrize (:issue:`634`).
|
* Fixed scope overriding inside metafunc.parametrize (:issue:`634`).
|
||||||
Thanks to :user:`Stranger6667` for the PR.
|
Thanks to :user:`Stranger6667` for the PR.
|
||||||
|
|
||||||
* Fixed the total tests tally in junit xml output (:pr:`1798`).
|
* Fixed the total tests tally in junit xml output (:pull:`1798`).
|
||||||
Thanks to :user:`cboelsen` for the PR.
|
Thanks to :user:`cboelsen` for the PR.
|
||||||
|
|
||||||
* Fixed off-by-one error with lines from ``request.node.warn``.
|
* Fixed off-by-one error with lines from ``request.node.warn``.
|
||||||
|
|
@ -7888,14 +7804,14 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
|
|
||||||
* Fix Xfail does not work with condition keyword argument.
|
* Fix Xfail does not work with condition keyword argument.
|
||||||
Thanks :user:`astraw38` for reporting the issue (:issue:`1496`) and :user:`tomviner`
|
Thanks :user:`astraw38` for reporting the issue (:issue:`1496`) and :user:`tomviner`
|
||||||
for PR the (:pr:`1524`).
|
for PR the (:pull:`1524`).
|
||||||
|
|
||||||
* Fix win32 path issue when putting custom config file with absolute path
|
* Fix win32 path issue when putting custom config file with absolute path
|
||||||
in ``pytest.main("-c your_absolute_path")``.
|
in ``pytest.main("-c your_absolute_path")``.
|
||||||
|
|
||||||
* Fix maximum recursion depth detection when raised error class is not aware
|
* Fix maximum recursion depth detection when raised error class is not aware
|
||||||
of unicode/encoded bytes.
|
of unicode/encoded bytes.
|
||||||
Thanks :user:`prusse-martin` for the PR (:pr:`1506`).
|
Thanks :user:`prusse-martin` for the PR (:pull:`1506`).
|
||||||
|
|
||||||
* Fix ``pytest.mark.skip`` mark when used in strict mode.
|
* Fix ``pytest.mark.skip`` mark when used in strict mode.
|
||||||
Thanks :user:`pquentin` for the PR and :user:`RonnyPfannschmidt` for
|
Thanks :user:`pquentin` for the PR and :user:`RonnyPfannschmidt` for
|
||||||
|
|
@ -7922,7 +7838,7 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
Thanks :user:`nicoddemus` for the PR.
|
Thanks :user:`nicoddemus` for the PR.
|
||||||
|
|
||||||
* Fix (:issue:`469`): junit parses report.nodeid incorrectly, when params IDs
|
* Fix (:issue:`469`): junit parses report.nodeid incorrectly, when params IDs
|
||||||
contain ``::``. Thanks :user:`tomviner` for the PR (:pr:`1431`).
|
contain ``::``. Thanks :user:`tomviner` for the PR (:pull:`1431`).
|
||||||
|
|
||||||
* Fix (:issue:`578`): SyntaxErrors
|
* Fix (:issue:`578`): SyntaxErrors
|
||||||
containing non-ascii lines at the point of failure generated an internal
|
containing non-ascii lines at the point of failure generated an internal
|
||||||
|
|
@ -7943,7 +7859,7 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
**New Features**
|
**New Features**
|
||||||
|
|
||||||
* New ``pytest.mark.skip`` mark, which unconditionally skips marked tests.
|
* New ``pytest.mark.skip`` mark, which unconditionally skips marked tests.
|
||||||
Thanks :user:`MichaelAquilina` for the complete PR (:pr:`1040`).
|
Thanks :user:`MichaelAquilina` for the complete PR (:pull:`1040`).
|
||||||
|
|
||||||
* ``--doctest-glob`` may now be passed multiple times in the command-line.
|
* ``--doctest-glob`` may now be passed multiple times in the command-line.
|
||||||
Thanks :user:`jab` and :user:`nicoddemus` for the PR.
|
Thanks :user:`jab` and :user:`nicoddemus` for the PR.
|
||||||
|
|
@ -7954,14 +7870,14 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
* ``pytest.mark.xfail`` now has a ``strict`` option, which makes ``XPASS``
|
* ``pytest.mark.xfail`` now has a ``strict`` option, which makes ``XPASS``
|
||||||
tests to fail the test suite (defaulting to ``False``). There's also a
|
tests to fail the test suite (defaulting to ``False``). There's also a
|
||||||
``xfail_strict`` ini option that can be used to configure it project-wise.
|
``xfail_strict`` ini option that can be used to configure it project-wise.
|
||||||
Thanks :user:`rabbbit` for the request and :user:`nicoddemus` for the PR (:pr:`1355`).
|
Thanks :user:`rabbbit` for the request and :user:`nicoddemus` for the PR (:pull:`1355`).
|
||||||
|
|
||||||
* ``Parser.addini`` now supports options of type ``bool``.
|
* ``Parser.addini`` now supports options of type ``bool``.
|
||||||
Thanks :user:`nicoddemus` for the PR.
|
Thanks :user:`nicoddemus` for the PR.
|
||||||
|
|
||||||
* New ``ALLOW_BYTES`` doctest option. This strips ``b`` prefixes from byte strings
|
* New ``ALLOW_BYTES`` doctest option. This strips ``b`` prefixes from byte strings
|
||||||
in doctest output (similar to ``ALLOW_UNICODE``).
|
in doctest output (similar to ``ALLOW_UNICODE``).
|
||||||
Thanks :user:`jaraco` for the request and :user:`nicoddemus` for the PR (:pr:`1287`).
|
Thanks :user:`jaraco` for the request and :user:`nicoddemus` for the PR (:pull:`1287`).
|
||||||
|
|
||||||
* Give a hint on ``KeyboardInterrupt`` to use the ``--fulltrace`` option to show the errors.
|
* Give a hint on ``KeyboardInterrupt`` to use the ``--fulltrace`` option to show the errors.
|
||||||
Fixes :issue:`1366`.
|
Fixes :issue:`1366`.
|
||||||
|
|
@ -7993,7 +7909,7 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
|
|
||||||
* Removed code and documentation for Python 2.5 or lower versions,
|
* Removed code and documentation for Python 2.5 or lower versions,
|
||||||
including removal of the obsolete ``_pytest.assertion.oldinterpret`` module.
|
including removal of the obsolete ``_pytest.assertion.oldinterpret`` module.
|
||||||
Thanks :user:`nicoddemus` for the PR (:pr:`1226`).
|
Thanks :user:`nicoddemus` for the PR (:pull:`1226`).
|
||||||
|
|
||||||
* Comparisons now always show up in full when ``CI`` or ``BUILD_NUMBER`` is
|
* Comparisons now always show up in full when ``CI`` or ``BUILD_NUMBER`` is
|
||||||
found in the environment, even when ``-vv`` isn't used.
|
found in the environment, even when ``-vv`` isn't used.
|
||||||
|
|
@ -8360,7 +8276,7 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
one will also have a "reprec" attribute with the recorded events/reports.
|
one will also have a "reprec" attribute with the recorded events/reports.
|
||||||
|
|
||||||
- fix monkeypatch.setattr("x.y", raising=False) to actually not raise
|
- fix monkeypatch.setattr("x.y", raising=False) to actually not raise
|
||||||
if "y" is not a preexisting attribute. Thanks Florian Bruhin.
|
if "y" is not a pre-existing attribute. Thanks Florian Bruhin.
|
||||||
|
|
||||||
- fix issue741: make running output from testdir.run copy/pasteable
|
- fix issue741: make running output from testdir.run copy/pasteable
|
||||||
Thanks Bruno Oliveira.
|
Thanks Bruno Oliveira.
|
||||||
|
|
@ -8416,7 +8332,7 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
|
|
||||||
- fix issue854: autouse yield_fixtures defined as class members of
|
- fix issue854: autouse yield_fixtures defined as class members of
|
||||||
unittest.TestCase subclasses now work as expected.
|
unittest.TestCase subclasses now work as expected.
|
||||||
Thanks xmo-odoo for the report and Bruno Oliveira for the PR.
|
Thannks xmo-odoo for the report and Bruno Oliveira for the PR.
|
||||||
|
|
||||||
- fix issue833: --fixtures now shows all fixtures of collected test files, instead of just the
|
- fix issue833: --fixtures now shows all fixtures of collected test files, instead of just the
|
||||||
fixtures declared on the first one.
|
fixtures declared on the first one.
|
||||||
|
|
@ -8520,7 +8436,7 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
github. See https://pytest.org/en/stable/contributing.html .
|
github. See https://pytest.org/en/stable/contributing.html .
|
||||||
Thanks to Anatoly for pushing and initial work on this.
|
Thanks to Anatoly for pushing and initial work on this.
|
||||||
|
|
||||||
- fix issue650: new option ``--doctest-ignore-import-errors`` which
|
- fix issue650: new option ``--docttest-ignore-import-errors`` which
|
||||||
will turn import errors in doctests into skips. Thanks Charles Cloud
|
will turn import errors in doctests into skips. Thanks Charles Cloud
|
||||||
for the complete PR.
|
for the complete PR.
|
||||||
|
|
||||||
|
|
@ -8708,7 +8624,7 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
- cleanup setup.py a bit and specify supported versions. Thanks Jurko
|
- cleanup setup.py a bit and specify supported versions. Thanks Jurko
|
||||||
Gospodnetic for the PR.
|
Gospodnetic for the PR.
|
||||||
|
|
||||||
- change XPASS colour to yellow rather than red when tests are run
|
- change XPASS colour to yellow rather then red when tests are run
|
||||||
with -v.
|
with -v.
|
||||||
|
|
||||||
- fix issue473: work around mock putting an unbound method into a class
|
- fix issue473: work around mock putting an unbound method into a class
|
||||||
|
|
@ -8881,7 +8797,7 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
Thanks Ralph Schmitt for the precise failure example.
|
Thanks Ralph Schmitt for the precise failure example.
|
||||||
|
|
||||||
- fix issue244 by implementing special index for parameters to only use
|
- fix issue244 by implementing special index for parameters to only use
|
||||||
indices for parametrized test ids
|
indices for paramentrized test ids
|
||||||
|
|
||||||
- fix issue287 by running all finalizers but saving the exception
|
- fix issue287 by running all finalizers but saving the exception
|
||||||
from the first failing finalizer and re-raising it so teardown will
|
from the first failing finalizer and re-raising it so teardown will
|
||||||
|
|
@ -8889,7 +8805,7 @@ time or change existing behaviors in order to make them less surprising/more use
|
||||||
it might be the cause for other finalizers to fail.
|
it might be the cause for other finalizers to fail.
|
||||||
|
|
||||||
- fix ordering when mock.patch or other standard decorator-wrappings
|
- fix ordering when mock.patch or other standard decorator-wrappings
|
||||||
are used with test methods. This fixes issue346 and should
|
are used with test methods. This fixues issue346 and should
|
||||||
help with random "xdist" collection failures. Thanks to
|
help with random "xdist" collection failures. Thanks to
|
||||||
Ronny Pfannschmidt and Donald Stufft for helping to isolate it.
|
Ronny Pfannschmidt and Donald Stufft for helping to isolate it.
|
||||||
|
|
||||||
|
|
@ -9146,7 +9062,7 @@ Bug fixes:
|
||||||
partially failed (finalizers would not always be called before)
|
partially failed (finalizers would not always be called before)
|
||||||
|
|
||||||
- fix issue320 - fix class scope for fixtures when mixed with
|
- fix issue320 - fix class scope for fixtures when mixed with
|
||||||
module-level functions. Thanks Anatoly Bubenkoff.
|
module-level functions. Thanks Anatloy Bubenkoff.
|
||||||
|
|
||||||
- you can specify "-q" or "-qq" to get different levels of "quieter"
|
- you can specify "-q" or "-qq" to get different levels of "quieter"
|
||||||
reporting (thanks Katarzyna Jachim)
|
reporting (thanks Katarzyna Jachim)
|
||||||
|
|
@ -9568,7 +9484,7 @@ Bug fixes:
|
||||||
unexpected exceptions
|
unexpected exceptions
|
||||||
- fix issue47: timing output in junitxml for test cases is now correct
|
- fix issue47: timing output in junitxml for test cases is now correct
|
||||||
- fix issue48: typo in MarkInfo repr leading to exception
|
- fix issue48: typo in MarkInfo repr leading to exception
|
||||||
- fix issue49: avoid confusing error when initialization partially fails
|
- fix issue49: avoid confusing error when initizaliation partially fails
|
||||||
- fix issue44: env/username expansion for junitxml file path
|
- fix issue44: env/username expansion for junitxml file path
|
||||||
- show releaselevel information in test runs for pypy
|
- show releaselevel information in test runs for pypy
|
||||||
- reworked doc pages for better navigation and PDF generation
|
- reworked doc pages for better navigation and PDF generation
|
||||||
|
|
@ -9693,7 +9609,7 @@ Bug fixes:
|
||||||
collection-before-running semantics were not
|
collection-before-running semantics were not
|
||||||
setup as with pytest 1.3.4. Note, however, that
|
setup as with pytest 1.3.4. Note, however, that
|
||||||
the recommended and much cleaner way to do test
|
the recommended and much cleaner way to do test
|
||||||
parameterization remains the "pytest_generate_tests"
|
parametraization remains the "pytest_generate_tests"
|
||||||
mechanism, see the docs.
|
mechanism, see the docs.
|
||||||
|
|
||||||
2.0.0 (2010-11-25)
|
2.0.0 (2010-11-25)
|
||||||
|
|
|
||||||
106
doc/en/conf.py
106
doc/en/conf.py
|
|
@ -15,33 +15,19 @@
|
||||||
#
|
#
|
||||||
# The full version, including alpha/beta/rc tags.
|
# The full version, including alpha/beta/rc tags.
|
||||||
# The short X.Y version.
|
# The short X.Y version.
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
import os
|
import os
|
||||||
from pathlib import Path
|
|
||||||
import shutil
|
import shutil
|
||||||
|
import sys
|
||||||
from textwrap import dedent
|
from textwrap import dedent
|
||||||
from typing import TYPE_CHECKING
|
from typing import TYPE_CHECKING
|
||||||
|
|
||||||
from _pytest import __version__ as full_version
|
from _pytest import __version__ as version
|
||||||
|
|
||||||
|
|
||||||
version = full_version.split("+")[0]
|
|
||||||
|
|
||||||
if TYPE_CHECKING:
|
if TYPE_CHECKING:
|
||||||
import sphinx.application
|
import sphinx.application
|
||||||
|
|
||||||
|
|
||||||
PROJECT_ROOT_DIR = Path(__file__).parents[2].resolve()
|
|
||||||
IS_RELEASE_ON_RTD = (
|
|
||||||
os.getenv("READTHEDOCS", "False") == "True"
|
|
||||||
and os.environ["READTHEDOCS_VERSION_TYPE"] == "tag"
|
|
||||||
)
|
|
||||||
if IS_RELEASE_ON_RTD:
|
|
||||||
tags: set[str]
|
|
||||||
# pylint: disable-next=used-before-assignment
|
|
||||||
tags.add("is_release") # noqa: F821
|
|
||||||
|
|
||||||
release = ".".join(version.split(".")[:2])
|
release = ".".join(version.split(".")[:2])
|
||||||
|
|
||||||
# If extensions (or modules to document with autodoc) are in another directory,
|
# If extensions (or modules to document with autodoc) are in another directory,
|
||||||
|
|
@ -79,16 +65,16 @@ latex_elements = {
|
||||||
# Add any Sphinx extension module names here, as strings. They can be extensions
|
# Add any Sphinx extension module names here, as strings. They can be extensions
|
||||||
# coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
|
# coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
|
||||||
extensions = [
|
extensions = [
|
||||||
|
"pallets_sphinx_themes",
|
||||||
"pygments_pytest",
|
"pygments_pytest",
|
||||||
"sphinx.ext.autodoc",
|
"sphinx.ext.autodoc",
|
||||||
"sphinx.ext.autosummary",
|
"sphinx.ext.autosummary",
|
||||||
|
"sphinx.ext.extlinks",
|
||||||
"sphinx.ext.intersphinx",
|
"sphinx.ext.intersphinx",
|
||||||
"sphinx.ext.todo",
|
"sphinx.ext.todo",
|
||||||
"sphinx.ext.viewcode",
|
"sphinx.ext.viewcode",
|
||||||
"sphinx_removed_in",
|
"sphinx_removed_in",
|
||||||
"sphinxcontrib_trio",
|
"sphinxcontrib_trio",
|
||||||
"sphinxcontrib.towncrier.ext", # provides `towncrier-draft-entries` directive
|
|
||||||
"sphinx_issues", # implements `:issue:`, `:pr:` and other GH-related roles
|
|
||||||
]
|
]
|
||||||
|
|
||||||
# Building PDF docs on readthedocs requires inkscape for svg to pdf
|
# Building PDF docs on readthedocs requires inkscape for svg to pdf
|
||||||
|
|
@ -154,6 +140,10 @@ add_module_names = False
|
||||||
# output. They are ignored by default.
|
# output. They are ignored by default.
|
||||||
# show_authors = False
|
# show_authors = False
|
||||||
|
|
||||||
|
# The name of the Pygments (syntax highlighting) style to use.
|
||||||
|
pygments_style = "sphinx"
|
||||||
|
|
||||||
|
|
||||||
# A list of ignored prefixes for module index sorting.
|
# A list of ignored prefixes for module index sorting.
|
||||||
# modindex_common_prefix = []
|
# modindex_common_prefix = []
|
||||||
|
|
||||||
|
|
@ -170,6 +160,16 @@ linkcheck_ignore = [
|
||||||
linkcheck_workers = 5
|
linkcheck_workers = 5
|
||||||
|
|
||||||
|
|
||||||
|
_repo = "https://github.com/pytest-dev/pytest"
|
||||||
|
extlinks = {
|
||||||
|
"bpo": ("https://bugs.python.org/issue%s", "bpo-%s"),
|
||||||
|
"pypi": ("https://pypi.org/project/%s/", "%s"),
|
||||||
|
"issue": (f"{_repo}/issues/%s", "issue #%s"),
|
||||||
|
"pull": (f"{_repo}/pull/%s", "pull request #%s"),
|
||||||
|
"user": ("https://github.com/%s", "@%s"),
|
||||||
|
}
|
||||||
|
|
||||||
|
|
||||||
nitpicky = True
|
nitpicky = True
|
||||||
nitpick_ignore = [
|
nitpick_ignore = [
|
||||||
# TODO (fix in pluggy?)
|
# TODO (fix in pluggy?)
|
||||||
|
|
@ -183,7 +183,6 @@ nitpick_ignore = [
|
||||||
("py:class", "SubRequest"),
|
("py:class", "SubRequest"),
|
||||||
("py:class", "TerminalReporter"),
|
("py:class", "TerminalReporter"),
|
||||||
("py:class", "_pytest._code.code.TerminalRepr"),
|
("py:class", "_pytest._code.code.TerminalRepr"),
|
||||||
("py:class", "TerminalRepr"),
|
|
||||||
("py:class", "_pytest.fixtures.FixtureFunctionMarker"),
|
("py:class", "_pytest.fixtures.FixtureFunctionMarker"),
|
||||||
("py:class", "_pytest.logging.LogCaptureHandler"),
|
("py:class", "_pytest.logging.LogCaptureHandler"),
|
||||||
("py:class", "_pytest.mark.structures.ParameterSet"),
|
("py:class", "_pytest.mark.structures.ParameterSet"),
|
||||||
|
|
@ -205,24 +204,24 @@ nitpick_ignore = [
|
||||||
("py:class", "_PluggyPlugin"),
|
("py:class", "_PluggyPlugin"),
|
||||||
# TypeVars
|
# TypeVars
|
||||||
("py:class", "_pytest._code.code.E"),
|
("py:class", "_pytest._code.code.E"),
|
||||||
("py:class", "E"), # due to delayed annotation
|
|
||||||
("py:class", "_pytest.fixtures.FixtureFunction"),
|
("py:class", "_pytest.fixtures.FixtureFunction"),
|
||||||
("py:class", "_pytest.nodes._NodeType"),
|
("py:class", "_pytest.nodes._NodeType"),
|
||||||
("py:class", "_NodeType"), # due to delayed annotation
|
|
||||||
("py:class", "_pytest.python_api.E"),
|
("py:class", "_pytest.python_api.E"),
|
||||||
("py:class", "_pytest.recwarn.T"),
|
("py:class", "_pytest.recwarn.T"),
|
||||||
("py:class", "_pytest.runner.TResult"),
|
("py:class", "_pytest.runner.TResult"),
|
||||||
("py:obj", "_pytest.fixtures.FixtureValue"),
|
("py:obj", "_pytest.fixtures.FixtureValue"),
|
||||||
("py:obj", "_pytest.stash.T"),
|
("py:obj", "_pytest.stash.T"),
|
||||||
("py:class", "_ScopeName"),
|
|
||||||
]
|
]
|
||||||
|
|
||||||
|
|
||||||
# -- Options for HTML output ---------------------------------------------------
|
# -- Options for HTML output ---------------------------------------------------
|
||||||
|
|
||||||
|
sys.path.append(os.path.abspath("_themes"))
|
||||||
|
html_theme_path = ["_themes"]
|
||||||
|
|
||||||
# The theme to use for HTML and HTML Help pages. See the documentation for
|
# The theme to use for HTML and HTML Help pages. See the documentation for
|
||||||
# a list of builtin themes.
|
# a list of builtin themes.
|
||||||
html_theme = "furo"
|
html_theme = "flask"
|
||||||
|
|
||||||
# Theme options are theme-specific and customize the look and feel of a theme
|
# Theme options are theme-specific and customize the look and feel of a theme
|
||||||
# further. For a list of options available for each theme, see the
|
# further. For a list of options available for each theme, see the
|
||||||
|
|
@ -267,24 +266,18 @@ html_favicon = "img/favicon.png"
|
||||||
|
|
||||||
html_sidebars = {
|
html_sidebars = {
|
||||||
"index": [
|
"index": [
|
||||||
"sidebar/brand.html",
|
"slim_searchbox.html",
|
||||||
"sidebar/search.html",
|
|
||||||
"sidebar/scroll-start.html",
|
|
||||||
"sidebarintro.html",
|
"sidebarintro.html",
|
||||||
"globaltoc.html",
|
"globaltoc.html",
|
||||||
"links.html",
|
"links.html",
|
||||||
"sidebar/scroll-end.html",
|
"sourcelink.html",
|
||||||
"style.html",
|
|
||||||
],
|
],
|
||||||
"**": [
|
"**": [
|
||||||
"sidebar/brand.html",
|
"slim_searchbox.html",
|
||||||
"sidebar/search.html",
|
|
||||||
"sidebar/scroll-start.html",
|
|
||||||
"globaltoc.html",
|
"globaltoc.html",
|
||||||
"relations.html",
|
"relations.html",
|
||||||
"links.html",
|
"links.html",
|
||||||
"sidebar/scroll-end.html",
|
"sourcelink.html",
|
||||||
"style.html",
|
|
||||||
],
|
],
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
@ -323,9 +316,6 @@ html_show_sourcelink = False
|
||||||
# Output file base name for HTML help builder.
|
# Output file base name for HTML help builder.
|
||||||
htmlhelp_basename = "pytestdoc"
|
htmlhelp_basename = "pytestdoc"
|
||||||
|
|
||||||
# The base URL which points to the root of the HTML documentation. It is used
|
|
||||||
# to indicate the location of document using the canonical link relation (#12363).
|
|
||||||
html_baseurl = "https://docs.pytest.org/en/stable/"
|
|
||||||
|
|
||||||
# -- Options for LaTeX output --------------------------------------------------
|
# -- Options for LaTeX output --------------------------------------------------
|
||||||
|
|
||||||
|
|
@ -347,6 +337,10 @@ latex_documents = [
|
||||||
)
|
)
|
||||||
]
|
]
|
||||||
|
|
||||||
|
# The name of an image file (relative to this directory) to place at the top of
|
||||||
|
# the title page.
|
||||||
|
latex_logo = "img/pytest1.png"
|
||||||
|
|
||||||
# For "manual" documents, if this is true, then toplevel headings are parts,
|
# For "manual" documents, if this is true, then toplevel headings are parts,
|
||||||
# not chapters.
|
# not chapters.
|
||||||
# latex_use_parts = False
|
# latex_use_parts = False
|
||||||
|
|
@ -433,18 +427,6 @@ texinfo_documents = [
|
||||||
)
|
)
|
||||||
]
|
]
|
||||||
|
|
||||||
# -- Options for towncrier_draft extension -----------------------------------
|
|
||||||
|
|
||||||
towncrier_draft_autoversion_mode = "draft" # or: 'sphinx-version', 'sphinx-release'
|
|
||||||
towncrier_draft_include_empty = True
|
|
||||||
towncrier_draft_working_directory = PROJECT_ROOT_DIR
|
|
||||||
towncrier_draft_config_path = "pyproject.toml" # relative to cwd
|
|
||||||
|
|
||||||
|
|
||||||
# -- Options for sphinx_issues extension -----------------------------------
|
|
||||||
|
|
||||||
issues_github_path = "pytest-dev/pytest"
|
|
||||||
|
|
||||||
|
|
||||||
intersphinx_mapping = {
|
intersphinx_mapping = {
|
||||||
"pluggy": ("https://pluggy.readthedocs.io/en/stable", None),
|
"pluggy": ("https://pluggy.readthedocs.io/en/stable", None),
|
||||||
|
|
@ -458,7 +440,31 @@ intersphinx_mapping = {
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
||||||
def setup(app: sphinx.application.Sphinx) -> None:
|
def configure_logging(app: "sphinx.application.Sphinx") -> None:
|
||||||
|
"""Configure Sphinx's WarningHandler to handle (expected) missing include."""
|
||||||
|
import logging
|
||||||
|
|
||||||
|
import sphinx.util.logging
|
||||||
|
|
||||||
|
class WarnLogFilter(logging.Filter):
|
||||||
|
def filter(self, record: logging.LogRecord) -> bool:
|
||||||
|
"""Ignore warnings about missing include with "only" directive.
|
||||||
|
|
||||||
|
Ref: https://github.com/sphinx-doc/sphinx/issues/2150."""
|
||||||
|
if (
|
||||||
|
record.msg.startswith('Problems with "include" directive path:')
|
||||||
|
and "_changelog_towncrier_draft.rst" in record.msg
|
||||||
|
):
|
||||||
|
return False
|
||||||
|
return True
|
||||||
|
|
||||||
|
logger = logging.getLogger(sphinx.util.logging.NAMESPACE)
|
||||||
|
warn_handler = [x for x in logger.handlers if x.level == logging.WARNING]
|
||||||
|
assert len(warn_handler) == 1, warn_handler
|
||||||
|
warn_handler[0].filters.insert(0, WarnLogFilter())
|
||||||
|
|
||||||
|
|
||||||
|
def setup(app: "sphinx.application.Sphinx") -> None:
|
||||||
app.add_crossref_type(
|
app.add_crossref_type(
|
||||||
"fixture",
|
"fixture",
|
||||||
"fixture",
|
"fixture",
|
||||||
|
|
@ -487,6 +493,8 @@ def setup(app: sphinx.application.Sphinx) -> None:
|
||||||
indextemplate="pair: %s; hook",
|
indextemplate="pair: %s; hook",
|
||||||
)
|
)
|
||||||
|
|
||||||
|
configure_logging(app)
|
||||||
|
|
||||||
# legacypath.py monkey-patches pytest.Testdir in. Import the file so
|
# legacypath.py monkey-patches pytest.Testdir in. Import the file so
|
||||||
# that autodoc can discover references to it.
|
# that autodoc can discover references to it.
|
||||||
import _pytest.legacypath # noqa: F401
|
import _pytest.legacypath # noqa: F401
|
||||||
|
|
|
||||||
|
|
@ -1,4 +1 @@
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
|
|
||||||
collect_ignore = ["conf.py"]
|
collect_ignore = ["conf.py"]
|
||||||
|
|
|
||||||
|
|
@ -22,16 +22,23 @@ Contact channels
|
||||||
requests to GitHub.
|
requests to GitHub.
|
||||||
|
|
||||||
- ``#pytest`` `on irc.libera.chat <ircs://irc.libera.chat:6697/#pytest>`_ IRC
|
- ``#pytest`` `on irc.libera.chat <ircs://irc.libera.chat:6697/#pytest>`_ IRC
|
||||||
channel for random questions (using an IRC client, or `via webchat
|
channel for random questions (using an IRC client, `via webchat
|
||||||
<https://web.libera.chat/#pytest>`)
|
<https://web.libera.chat/#pytest>`_, or `via Matrix
|
||||||
- ``#pytest`` `on Matrix https://matrix.to/#/#pytest:matrix.org>`.
|
<https://matrix.to/#/%23pytest:libera.chat>`_).
|
||||||
|
|
||||||
|
- private mail to Holger.Krekel at gmail com if you want to communicate sensitive issues
|
||||||
|
|
||||||
|
|
||||||
|
- `merlinux.eu`_ offers pytest and tox-related professional teaching and
|
||||||
|
consulting.
|
||||||
|
|
||||||
.. _`pytest issue tracker`: https://github.com/pytest-dev/pytest/issues
|
.. _`pytest issue tracker`: https://github.com/pytest-dev/pytest/issues
|
||||||
.. _`old issue tracker`: https://bitbucket.org/hpk42/py-trunk/issues/
|
.. _`old issue tracker`: https://bitbucket.org/hpk42/py-trunk/issues/
|
||||||
|
|
||||||
.. _`pytest discussions`: https://github.com/pytest-dev/pytest/discussions
|
.. _`pytest discussions`: https://github.com/pytest-dev/pytest/discussions
|
||||||
|
|
||||||
|
.. _`merlinux.eu`: https://merlinux.eu/
|
||||||
|
|
||||||
.. _`get an account`:
|
.. _`get an account`:
|
||||||
|
|
||||||
.. _tetamap: https://tetamap.wordpress.com/
|
.. _tetamap: https://tetamap.wordpress.com/
|
||||||
|
|
|
||||||
|
|
@ -7,6 +7,10 @@ This page lists all pytest features that are currently deprecated or have been r
|
||||||
The objective is to give users a clear rationale why a certain feature has been removed, and what alternatives
|
The objective is to give users a clear rationale why a certain feature has been removed, and what alternatives
|
||||||
should be used instead.
|
should be used instead.
|
||||||
|
|
||||||
|
.. contents::
|
||||||
|
:depth: 3
|
||||||
|
:local:
|
||||||
|
|
||||||
|
|
||||||
Deprecated Features
|
Deprecated Features
|
||||||
-------------------
|
-------------------
|
||||||
|
|
@ -458,7 +462,7 @@ Now :class:`~pytest.Class` collects the test methods directly.
|
||||||
Most plugins which reference ``Instance`` do so in order to ignore or skip it,
|
Most plugins which reference ``Instance`` do so in order to ignore or skip it,
|
||||||
using a check such as ``if isinstance(node, Instance): return``.
|
using a check such as ``if isinstance(node, Instance): return``.
|
||||||
Such plugins should simply remove consideration of ``Instance`` on pytest>=7.
|
Such plugins should simply remove consideration of ``Instance`` on pytest>=7.
|
||||||
However, to keep such uses working, a dummy type has been instanced in ``pytest.Instance`` and ``_pytest.python.Instance``,
|
However, to keep such uses working, a dummy type has been instanted in ``pytest.Instance`` and ``_pytest.python.Instance``,
|
||||||
and importing it emits a deprecation warning. This was removed in pytest 8.
|
and importing it emits a deprecation warning. This was removed in pytest 8.
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,5 +1,3 @@
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
import pytest
|
import pytest
|
||||||
from pytest import raises
|
from pytest import raises
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,5 +1,3 @@
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
import os.path
|
import os.path
|
||||||
|
|
||||||
import pytest
|
import pytest
|
||||||
|
|
|
||||||
|
|
@ -1,6 +1,3 @@
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
|
|
||||||
hello = "world"
|
hello = "world"
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,5 +1,3 @@
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
import os.path
|
import os.path
|
||||||
import shutil
|
import shutil
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,6 +1,3 @@
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
|
|
||||||
def setup_module(module):
|
def setup_module(module):
|
||||||
module.TestStateFullThing.classcount = 0
|
module.TestStateFullThing.classcount = 0
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,4 +1 @@
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
|
|
||||||
collect_ignore = ["nonpython", "customdirectory"]
|
collect_ignore = ["nonpython", "customdirectory"]
|
||||||
|
|
|
||||||
|
|
@ -1,6 +1,4 @@
|
||||||
# content of conftest.py
|
# content of conftest.py
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
import json
|
import json
|
||||||
|
|
||||||
import pytest
|
import pytest
|
||||||
|
|
@ -23,7 +21,7 @@ class ManifestDirectory(pytest.Directory):
|
||||||
|
|
||||||
@pytest.hookimpl
|
@pytest.hookimpl
|
||||||
def pytest_collect_directory(path, parent):
|
def pytest_collect_directory(path, parent):
|
||||||
# Use our custom collector for directories containing a `manifest.json` file.
|
# Use our custom collector for directories containing a `mainfest.json` file.
|
||||||
if path.joinpath("manifest.json").is_file():
|
if path.joinpath("manifest.json").is_file():
|
||||||
return ManifestDirectory.from_parent(parent=parent, path=path)
|
return ManifestDirectory.from_parent(parent=parent, path=path)
|
||||||
# Otherwise fallback to the standard behavior.
|
# Otherwise fallback to the standard behavior.
|
||||||
|
|
|
||||||
|
|
@ -1,6 +1,3 @@
|
||||||
# content of test_first.py
|
# content of test_first.py
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
|
|
||||||
def test_1():
|
def test_1():
|
||||||
pass
|
pass
|
||||||
|
|
|
||||||
|
|
@ -1,6 +1,3 @@
|
||||||
# content of test_second.py
|
# content of test_second.py
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
|
|
||||||
def test_2():
|
def test_2():
|
||||||
pass
|
pass
|
||||||
|
|
|
||||||
|
|
@ -1,6 +1,3 @@
|
||||||
# content of test_third.py
|
# content of test_third.py
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
|
|
||||||
def test_3():
|
def test_3():
|
||||||
pass
|
pass
|
||||||
|
|
|
||||||
|
|
@ -1,5 +1,3 @@
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
import pytest
|
import pytest
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,5 +1,3 @@
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
import pytest
|
import pytest
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,5 +1,3 @@
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
import pytest
|
import pytest
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,5 +1,3 @@
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
import pytest
|
import pytest
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,5 +1,3 @@
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
import pytest
|
import pytest
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,5 +1,3 @@
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
import pytest
|
import pytest
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -25,12 +25,10 @@ You can "mark" a test function with custom metadata like this:
|
||||||
pass # perform some webtest test for your app
|
pass # perform some webtest test for your app
|
||||||
|
|
||||||
|
|
||||||
@pytest.mark.device(serial="123")
|
|
||||||
def test_something_quick():
|
def test_something_quick():
|
||||||
pass
|
pass
|
||||||
|
|
||||||
|
|
||||||
@pytest.mark.device(serial="abc")
|
|
||||||
def test_another():
|
def test_another():
|
||||||
pass
|
pass
|
||||||
|
|
||||||
|
|
@ -73,28 +71,6 @@ Or the inverse, running all tests except the webtest ones:
|
||||||
|
|
||||||
===================== 3 passed, 1 deselected in 0.12s ======================
|
===================== 3 passed, 1 deselected in 0.12s ======================
|
||||||
|
|
||||||
.. _`marker_keyword_expression_example`:
|
|
||||||
|
|
||||||
Additionally, you can restrict a test run to only run tests matching one or multiple marker
|
|
||||||
keyword arguments, e.g. to run only tests marked with ``device`` and the specific ``serial="123"``:
|
|
||||||
|
|
||||||
.. code-block:: pytest
|
|
||||||
|
|
||||||
$ pytest -v -m "device(serial='123')"
|
|
||||||
=========================== test session starts ============================
|
|
||||||
platform linux -- Python 3.x.y, pytest-8.x.y, pluggy-1.x.y -- $PYTHON_PREFIX/bin/python
|
|
||||||
cachedir: .pytest_cache
|
|
||||||
rootdir: /home/sweet/project
|
|
||||||
collecting ... collected 4 items / 3 deselected / 1 selected
|
|
||||||
|
|
||||||
test_server.py::test_something_quick PASSED [100%]
|
|
||||||
|
|
||||||
===================== 1 passed, 3 deselected in 0.12s ======================
|
|
||||||
|
|
||||||
.. note:: Only keyword argument matching is supported in marker expressions.
|
|
||||||
|
|
||||||
.. note:: Only :class:`int`, (unescaped) :class:`str`, :class:`bool` & :data:`None` values are supported in marker expressions.
|
|
||||||
|
|
||||||
Selecting tests based on their node ID
|
Selecting tests based on their node ID
|
||||||
--------------------------------------
|
--------------------------------------
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,6 @@
|
||||||
"""Module containing a parametrized tests testing cross-python serialization
|
"""Module containing a parametrized tests testing cross-python serialization
|
||||||
via the pickle module."""
|
via the pickle module."""
|
||||||
|
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
import shutil
|
import shutil
|
||||||
import subprocess
|
import subprocess
|
||||||
import textwrap
|
import textwrap
|
||||||
|
|
|
||||||
|
|
@ -1,6 +1,4 @@
|
||||||
# content of conftest.py
|
# content of conftest.py
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
import pytest
|
import pytest
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -162,7 +162,7 @@ objects, they are still using the default pytest representation:
|
||||||
rootdir: /home/sweet/project
|
rootdir: /home/sweet/project
|
||||||
collected 8 items
|
collected 8 items
|
||||||
|
|
||||||
<Dir parametrize.rst-200>
|
<Dir parametrize.rst-198>
|
||||||
<Module test_time.py>
|
<Module test_time.py>
|
||||||
<Function test_timedistance_v0[a0-b0-expected0]>
|
<Function test_timedistance_v0[a0-b0-expected0]>
|
||||||
<Function test_timedistance_v0[a1-b1-expected1]>
|
<Function test_timedistance_v0[a1-b1-expected1]>
|
||||||
|
|
@ -239,7 +239,7 @@ If you just collect tests you'll also nicely see 'advanced' and 'basic' as varia
|
||||||
rootdir: /home/sweet/project
|
rootdir: /home/sweet/project
|
||||||
collected 4 items
|
collected 4 items
|
||||||
|
|
||||||
<Dir parametrize.rst-200>
|
<Dir parametrize.rst-198>
|
||||||
<Module test_scenarios.py>
|
<Module test_scenarios.py>
|
||||||
<Class TestSampleWithScenarios>
|
<Class TestSampleWithScenarios>
|
||||||
<Function test_demo1[basic]>
|
<Function test_demo1[basic]>
|
||||||
|
|
@ -318,7 +318,7 @@ Let's first see how it looks like at collection time:
|
||||||
rootdir: /home/sweet/project
|
rootdir: /home/sweet/project
|
||||||
collected 2 items
|
collected 2 items
|
||||||
|
|
||||||
<Dir parametrize.rst-200>
|
<Dir parametrize.rst-198>
|
||||||
<Module test_backends.py>
|
<Module test_backends.py>
|
||||||
<Function test_db_initialized[d1]>
|
<Function test_db_initialized[d1]>
|
||||||
<Function test_db_initialized[d2]>
|
<Function test_db_initialized[d2]>
|
||||||
|
|
|
||||||
|
|
@ -1,6 +1,5 @@
|
||||||
# run this with $ pytest --collect-only test_collectonly.py
|
# run this with $ pytest --collect-only test_collectonly.py
|
||||||
#
|
#
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
|
|
||||||
def test_function():
|
def test_function():
|
||||||
|
|
|
||||||
|
|
@ -152,7 +152,7 @@ The test collection would look like this:
|
||||||
configfile: pytest.ini
|
configfile: pytest.ini
|
||||||
collected 2 items
|
collected 2 items
|
||||||
|
|
||||||
<Dir pythoncollection.rst-201>
|
<Dir pythoncollection.rst-199>
|
||||||
<Module check_myapp.py>
|
<Module check_myapp.py>
|
||||||
<Class CheckMyApp>
|
<Class CheckMyApp>
|
||||||
<Function simple_check>
|
<Function simple_check>
|
||||||
|
|
@ -215,7 +215,7 @@ You can always peek at the collection tree without running tests like this:
|
||||||
configfile: pytest.ini
|
configfile: pytest.ini
|
||||||
collected 3 items
|
collected 3 items
|
||||||
|
|
||||||
<Dir pythoncollection.rst-201>
|
<Dir pythoncollection.rst-199>
|
||||||
<Dir CWD>
|
<Dir CWD>
|
||||||
<Module pythoncollection.py>
|
<Module pythoncollection.py>
|
||||||
<Function test_function>
|
<Function test_function>
|
||||||
|
|
|
||||||
|
|
@ -212,7 +212,7 @@ the command line arguments before they get processed:
|
||||||
|
|
||||||
.. code-block:: python
|
.. code-block:: python
|
||||||
|
|
||||||
# installable external plugin
|
# setuptools plugin
|
||||||
import sys
|
import sys
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -1073,8 +1073,8 @@ Instead of freezing the pytest runner as a separate executable, you can make
|
||||||
your frozen program work as the pytest runner by some clever
|
your frozen program work as the pytest runner by some clever
|
||||||
argument handling during program startup. This allows you to
|
argument handling during program startup. This allows you to
|
||||||
have a single executable, which is usually more convenient.
|
have a single executable, which is usually more convenient.
|
||||||
Please note that the mechanism for plugin discovery used by pytest (:ref:`entry
|
Please note that the mechanism for plugin discovery used by pytest
|
||||||
points <pip-installable plugins>`) doesn't work with frozen executables so pytest
|
(setuptools entry points) doesn't work with frozen executables so pytest
|
||||||
can't find any third party plugins automatically. To include third party plugins
|
can't find any third party plugins automatically. To include third party plugins
|
||||||
like ``pytest-timeout`` they must be imported explicitly and passed on to pytest.main.
|
like ``pytest-timeout`` they must be imported explicitly and passed on to pytest.main.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,5 +1,3 @@
|
||||||
from __future__ import annotations
|
|
||||||
|
|
||||||
import pytest
|
import pytest
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -18,7 +18,7 @@ System state
|
||||||
|
|
||||||
Broadly speaking, a flaky test indicates that the test relies on some system state that is not being appropriately controlled - the test environment is not sufficiently isolated. Higher level tests are more likely to be flaky as they rely on more state.
|
Broadly speaking, a flaky test indicates that the test relies on some system state that is not being appropriately controlled - the test environment is not sufficiently isolated. Higher level tests are more likely to be flaky as they rely on more state.
|
||||||
|
|
||||||
Flaky tests sometimes appear when a test suite is run in parallel (such as use of `pytest-xdist`_). This can indicate a test is reliant on test ordering.
|
Flaky tests sometimes appear when a test suite is run in parallel (such as use of pytest-xdist). This can indicate a test is reliant on test ordering.
|
||||||
|
|
||||||
- Perhaps a different test is failing to clean up after itself and leaving behind data which causes the flaky test to fail.
|
- Perhaps a different test is failing to clean up after itself and leaving behind data which causes the flaky test to fail.
|
||||||
- The flaky test is reliant on data from a previous test that doesn't clean up after itself, and in parallel runs that previous test is not always present
|
- The flaky test is reliant on data from a previous test that doesn't clean up after itself, and in parallel runs that previous test is not always present
|
||||||
|
|
@ -30,22 +30,9 @@ Overly strict assertion
|
||||||
|
|
||||||
Overly strict assertions can cause problems with floating point comparison as well as timing issues. :func:`pytest.approx` is useful here.
|
Overly strict assertions can cause problems with floating point comparison as well as timing issues. :func:`pytest.approx` is useful here.
|
||||||
|
|
||||||
Thread safety
|
|
||||||
~~~~~~~~~~~~~
|
|
||||||
|
|
||||||
pytest is single-threaded, executing its tests always in the same thread, sequentially, never spawning any threads itself.
|
Pytest features
|
||||||
|
^^^^^^^^^^^^^^^
|
||||||
Even in case of plugins which run tests in parallel, for example `pytest-xdist`_, usually work by spawning multiple *processes* and running tests in batches, without using multiple threads.
|
|
||||||
|
|
||||||
It is of course possible (and common) for tests and fixtures to spawn threads themselves as part of their testing workflow (for example, a fixture that starts a server thread in the background, or a test which executes production code that spawns threads), but some care must be taken:
|
|
||||||
|
|
||||||
* Make sure to eventually wait on any spawned threads -- for example at the end of a test, or during the teardown of a fixture.
|
|
||||||
* Avoid using primitives provided by pytest (:func:`pytest.warns`, :func:`pytest.raises`, etc) from multiple threads, as they are not thread-safe.
|
|
||||||
|
|
||||||
If your test suite uses threads and your are seeing flaky test results, do not discount the possibility that the test is implicitly using global state in pytest itself.
|
|
||||||
|
|
||||||
Related features
|
|
||||||
^^^^^^^^^^^^^^^^
|
|
||||||
|
|
||||||
Xfail strict
|
Xfail strict
|
||||||
~~~~~~~~~~~~
|
~~~~~~~~~~~~
|
||||||
|
|
@ -136,6 +123,3 @@ Resources
|
||||||
|
|
||||||
* `Flaky Tests at Google and How We Mitigate Them <https://testing.googleblog.com/2016/05/flaky-tests-at-google-and-how-we.html>`_ by John Micco, 2016
|
* `Flaky Tests at Google and How We Mitigate Them <https://testing.googleblog.com/2016/05/flaky-tests-at-google-and-how-we.html>`_ by John Micco, 2016
|
||||||
* `Where do Google's flaky tests come from? <https://testing.googleblog.com/2017/04/where-do-our-flaky-tests-come-from.html>`_ by Jeff Listfield, 2017
|
* `Where do Google's flaky tests come from? <https://testing.googleblog.com/2017/04/where-do-our-flaky-tests-come-from.html>`_ by Jeff Listfield, 2017
|
||||||
|
|
||||||
|
|
||||||
.. _pytest-xdist: https://github.com/pytest-dev/pytest-xdist
|
|
||||||
|
|
|
||||||
|
|
@ -8,15 +8,15 @@ pytest import mechanisms and ``sys.path``/``PYTHONPATH``
|
||||||
Import modes
|
Import modes
|
||||||
------------
|
------------
|
||||||
|
|
||||||
pytest as a testing framework that needs to import test modules and ``conftest.py`` files for execution.
|
pytest as a testing framework needs to import test modules and ``conftest.py`` files for execution.
|
||||||
|
|
||||||
Importing files in Python is a non-trivial process, so aspects of the
|
Importing files in Python is a non-trivial processes, so aspects of the
|
||||||
import process can be controlled through the ``--import-mode`` command-line flag, which can assume
|
import process can be controlled through the ``--import-mode`` command-line flag, which can assume
|
||||||
these values:
|
these values:
|
||||||
|
|
||||||
.. _`import-mode-prepend`:
|
.. _`import-mode-prepend`:
|
||||||
|
|
||||||
* ``prepend`` (default): The directory path containing each module will be inserted into the *beginning*
|
* ``prepend`` (default): the directory path containing each module will be inserted into the *beginning*
|
||||||
of :py:data:`sys.path` if not already there, and then imported with
|
of :py:data:`sys.path` if not already there, and then imported with
|
||||||
the :func:`importlib.import_module <importlib.import_module>` function.
|
the :func:`importlib.import_module <importlib.import_module>` function.
|
||||||
|
|
||||||
|
|
@ -34,7 +34,7 @@ these values:
|
||||||
* ``append``: the directory containing each module is appended to the end of :py:data:`sys.path` if not already
|
* ``append``: the directory containing each module is appended to the end of :py:data:`sys.path` if not already
|
||||||
there, and imported with :func:`importlib.import_module <importlib.import_module>`.
|
there, and imported with :func:`importlib.import_module <importlib.import_module>`.
|
||||||
|
|
||||||
This better allows users to run test modules against installed versions of a package even if the
|
This better allows to run test modules against installed versions of a package even if the
|
||||||
package under test has the same import root. For example:
|
package under test has the same import root. For example:
|
||||||
|
|
||||||
::
|
::
|
||||||
|
|
@ -45,7 +45,7 @@ these values:
|
||||||
|
|
||||||
the tests will run against the installed version
|
the tests will run against the installed version
|
||||||
of ``pkg_under_test`` when ``--import-mode=append`` is used whereas
|
of ``pkg_under_test`` when ``--import-mode=append`` is used whereas
|
||||||
with ``prepend``, they would pick up the local version. This kind of confusion is why
|
with ``prepend`` they would pick up the local version. This kind of confusion is why
|
||||||
we advocate for using :ref:`src-layouts <src-layout>`.
|
we advocate for using :ref:`src-layouts <src-layout>`.
|
||||||
|
|
||||||
Same as ``prepend``, requires test module names to be unique when the test directory tree is
|
Same as ``prepend``, requires test module names to be unique when the test directory tree is
|
||||||
|
|
@ -67,7 +67,7 @@ these values:
|
||||||
are not importable. The recommendation in this case it to place testing utility modules together with the application/library
|
are not importable. The recommendation in this case it to place testing utility modules together with the application/library
|
||||||
code, for example ``app.testing.helpers``.
|
code, for example ``app.testing.helpers``.
|
||||||
|
|
||||||
Important: by "test utility modules", we mean functions/classes which are imported by
|
Important: by "test utility modules" we mean functions/classes which are imported by
|
||||||
other tests directly; this does not include fixtures, which should be placed in ``conftest.py`` files, along
|
other tests directly; this does not include fixtures, which should be placed in ``conftest.py`` files, along
|
||||||
with the test modules, and are discovered automatically by pytest.
|
with the test modules, and are discovered automatically by pytest.
|
||||||
|
|
||||||
|
|
@ -76,8 +76,8 @@ these values:
|
||||||
1. Given a certain module path, for example ``tests/core/test_models.py``, derives a canonical name
|
1. Given a certain module path, for example ``tests/core/test_models.py``, derives a canonical name
|
||||||
like ``tests.core.test_models`` and tries to import it.
|
like ``tests.core.test_models`` and tries to import it.
|
||||||
|
|
||||||
For non-test modules, this will work if they are accessible via :py:data:`sys.path`. So
|
For non-test modules this will work if they are accessible via :py:data:`sys.path`, so
|
||||||
for example, ``.env/lib/site-packages/app/core.py`` will be importable as ``app.core``.
|
for example ``.env/lib/site-packages/app/core.py`` will be importable as ``app.core``.
|
||||||
This is happens when plugins import non-test modules (for example doctesting).
|
This is happens when plugins import non-test modules (for example doctesting).
|
||||||
|
|
||||||
If this step succeeds, the module is returned.
|
If this step succeeds, the module is returned.
|
||||||
|
|
|
||||||
|
|
@ -22,7 +22,7 @@ Install ``pytest``
|
||||||
.. code-block:: bash
|
.. code-block:: bash
|
||||||
|
|
||||||
$ pytest --version
|
$ pytest --version
|
||||||
pytest 8.2.2
|
pytest 8.2.0
|
||||||
|
|
||||||
.. _`simpletest`:
|
.. _`simpletest`:
|
||||||
|
|
||||||
|
|
@ -274,7 +274,7 @@ Continue reading
|
||||||
Check out additional pytest resources to help you customize tests for your unique workflow:
|
Check out additional pytest resources to help you customize tests for your unique workflow:
|
||||||
|
|
||||||
* ":ref:`usage`" for command line invocation examples
|
* ":ref:`usage`" for command line invocation examples
|
||||||
* ":ref:`existingtestsuite`" for working with preexisting tests
|
* ":ref:`existingtestsuite`" for working with pre-existing tests
|
||||||
* ":ref:`mark`" for information on the ``pytest.mark`` mechanism
|
* ":ref:`mark`" for information on the ``pytest.mark`` mechanism
|
||||||
* ":ref:`fixtures`" for providing a functional baseline to your tests
|
* ":ref:`fixtures`" for providing a functional baseline to your tests
|
||||||
* ":ref:`plugins`" for managing and writing plugins
|
* ":ref:`plugins`" for managing and writing plugins
|
||||||
|
|
|
||||||
|
|
@ -107,7 +107,7 @@ Here is a non-exhaustive list of issues fixed by the new implementation:
|
||||||
|
|
||||||
* Marker transfer incompatible with inheritance (:issue:`535`).
|
* Marker transfer incompatible with inheritance (:issue:`535`).
|
||||||
|
|
||||||
More details can be found in the :pr:`original PR <3317>`.
|
More details can be found in the :pull:`original PR <3317>`.
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
|
|
||||||
|
|
|
||||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue