pytest-dev / pytest-dev/pytest
warn when tests raise plain assertion errors without annotation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.5k
- Forks
- 3.4k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 35
Description
with the removal of reinterpretation,
we start to expose hard to comprehend issues
for example in #1929 its not clear at first, that the import inside of the conftest causes the rewriting of the test module to fail
in order to protect users we need to make them aware of those subtle issues
edit additionally the documentation on importing code in conf-tests should be revised
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading this issue and example #1929, then trace the test-module rewriting path and how imports from conftest.py produce plain assertion errors. Done means users receive a clear warning for this failure mode and the documentation on importing code in conftest files is revised.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100