Add a requirements.txt for testing dependency
Open
Nobody has claimed this yet.
enhancement
module: tests
- Dominant language
- Python
- Stars
- 17.9k
- Forks
- 7.3k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 13
Description
There are bunch of non-required deps which are needed to get full test coverage. It would be helpful if they were all collected somewhere, e.g., in a requirements.txt
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 test setup and existing dependency declarations, then identify the non-required packages needed for full test coverage. Add those packages to requirements.txt and run the test suite to confirm the listed dependencies support the tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, testing-qa
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100