pytest
pytest copied to clipboard
pytest-dev
The pytest framework makes it easy to write small tests, yet scales to support complex functional testing
- [x] a detailed description of the bug or problem you are having - [ ] output of `pip list` from the virtual environment you are using - [x] pytest...
Backport of PR #10143 to 7.1.x branch. PR created by backport workflow.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "github-actions[bot] avatar"){kind=avatar}
As discussed in https://github.com/pytest-dev/pytest/issues/9288#issuecomment-965102239, using `pytest.warns` will by design also capture `DeprecationWarning`s which would by default be captured by pytest. We should add a note about that in `pytest.warns` and...
`nose` has long been in maintenance only mode, and we support it via our `nose.py` plugin. The `nose.py` plugin however is not trivial to maintain, and it dips its toes...
this one carries a bug-fix for for the fixture lookup that we might want to add in general as well as a stacklevel ix for the terminalwriter deprecation if necessary...
addresses #8412 currently only a reproducer i suspect this relates to injected fixtures xunit functions should be in the same position as xunit fixtures xunit functions that are non autouse...
I think we can start planning the 7.2 schedule. I've created the [7.2 milestone](https://github.com/pytest-dev/pytest/milestone/40) so we can start assigning issues to it and track when 7.2 is ready. 👍 Also,...
#### What's the problem this feature will solve? Add typing information for parameterized fixtures to have better support for type checkers. #### Describe the solution you'd like Given a fixture...
Follow up from #1014. We should generate an error if a `@pytest.mark` is applied to a fixture. There is a warning in `doc/en/fixture.rst` about this problem which should be updated...
Metadata
Owner
Metadata
The pytest framework makes it easy to write small tests, yet scales to support complex functional testing