pytest-dev / pytest-dev/pytest
testsuite verification
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.5k
- Forks
- 3.4k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 35
Description
while doing a pr for removal of compatproperties and Generator tests
i ran into dozens of bad tests that don't test what they are supposed to test as well as a few duplicate tests that dont look duplicate
we should take a look at how bad the testsuite actually is, and shift it towards better practices
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 reviewing the tests related to compatproperties and Generator, which the issue identifies as sources of questionable coverage and possible duplication. Compare each test with the behavior it is intended to verify and document the scope of the broader suite review. Done means the affected tests genuinely check their intended behavior and duplicate coverage is resolved, but the issue does not name files or a bounded target.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100