pytest-plus 0.7.0

Description:

pytestplus 0.7.0

PyTest Plus Plugin :: extends pytest functionality




This plugin aims to be used to host multiple basic pytest extensions that meet
the following criteria:

Downgrade gracefully, meaning that if the plugin is removed, you will still
be able to run pytest

PYTEST_REQPASS
If you define environment variable PYTEST_REQPASS=123 and at the end of the
testing the number of passed tests is
not exactly 123, pytest will return exit code 1.
This feature is aimed for CI usage in order to prevent accidental skipping of
some tests. We do expect users to define this variable within their own CI job
definitions. The number of tests executed is likely to be dependent on the CI
job.
We discourage defining this inside places like tox.ini because when a
developer runs tests, they are likely to endup running a different number of
tests. Also, this feature makes no sense if you try to mention a specific test.
Avoiding duplicate test function names
While pytest allows users to have the same test function names in different
files, that makes it harder to identify and copy/paste the test name in order
to reproduce the failure locally. That is why this plugin forces its users to
avoid having the same function name anywhere in the tested project.
You can disable this check by defining PYTEST_CHECK_TEST_DUPLICATE=0.
Avoiding problematic test identifiers
This plugin will raise errors when it encounters test IDs that are either too
long or that contain unsafe characters. While pytest is very flexible in allowing
a wide range of test IDs, using these does make development harder as it prevents
people from doing a copy/paste with failed test and pasting in in their terminal
to reproduce the failed test locally.
You can disable regex check by defining PYTEST_CHECK_TEST_ID_REGEX=0.
You can disable the length check by defining PYTEST_MAX_TEST_ID_LENGTH=0.
Prepare pytest log files for collection on CI
As pytest log files are created on temp directory and some CI systems refuse
to collect files from outside the current project, we do copy these files inside
$VIRTUAL_ENV/log, same directory used by tox itself. To collect the logs on
Github Actions, you only need a step like:
- name: Archive logs
uses: actions/upload-artifact@v4
with:
name: logs-${{ matrix.name }}.zip
path: .tox/**/log/

Release process
Releases are triggered from GitHub Releases
page.
Links

MIT
file an issue
pytest
tox
pip
PyPI