pytest-dev / pytest-dev/pytest-django
Check for deprecation warnings in our test suite / CI
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 367
- PR merge metrics
- No merged PRs in 30d
Description
See #393 and #395 for warnings that we missed. We need a way to make sure we put out warning-free releases.
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 issues #393 and #395 to identify the deprecation warnings that were missed, then inspect the test suite and CI configuration for where warnings are currently handled. Done means the release checks reliably detect the relevant deprecation warnings and prevent warning-free releases from being missed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100