Add unit tests for scripts in `tests/` and `scripts/`
Open
Nobody has claimed this yet.
project: infrastructure
- Dominant language
- Python
- Stars
- 5.1k
- Forks
- 2.1k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 82
Description
Some of our scripts in the tests/ and scripts/ directories are increasingly subtle. It's becoming increasingly hard to refactor and improve some of them without breaking them in unexpected ways.
I'd like to add some unit tests for some of these scripts, to help address this. Does that sound like a good idea?
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 scripts in the tests/ and scripts/ directories and identify which behaviors are subtle or risky to change. Define a focused set of unit tests for selected scripts; the work is done when those tests protect their existing behavior and support safer refactoring.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100