pytest
pytest copied to clipboard
The pytest framework makes it easy to write small tests, yet scales to support complex functional testing
Ok, of course they are... But usually* when a dev commits the test, the test is passing, so the dev may not notice how preposterous a diff they are inadvertently...
- [x] junitxml fstrings - [x] skipping fstrings - [x] fixture test fstrings - [x] junitxml tests Domnode Refactoring (needs bikeshedding) this is a bunch of changes i collected as...
this is a initial prepare to mitigate the "smart ctors" for node types
Follow-up to #12427 plus some more cleanups: - Mention `[email protected]` as mail point of contact (not live yet, hence why this is a draft PR) - Also add a list...
This helps prevent testing the non-installed source. Additionally, the patch updates the docs to demonstrate a more predictable runpy-style invocation method.
We have quite some history when it comes to link checks: - #1722 - #5613 - #5614 - #6612 - #6916 So we're currently not running link checking at all....
Using an invalid regex in `pytest.raises` fails in a messy way. ```py with pytest.raises(ValueError, match="invalid regex character ["): raise ValueError() ``` ```shell Traceback (most recent call last): File "", line...
Suppose you have a parameterized test, some params of which are expected to raise (e.g.) `IndexError`: ```python return pytest.param( ..., marks=pytest.mark.xfail(raises=IndexError, strict=True), ) ``` If your test is async though,...
Closes [#11525](https://github.com/pytest-dev/pytest/issues/11525) During the sprint we discussed fixing the above issue and thought maybe it's a better idea to add a better represenation to fixtures. To do this without patching...