Test scripts and tracking scripts
Open
Nobody has claimed this yet.
CI
Testing
- Dominant language
- Python
- Stars
- 71
- Forks
- 27
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 33
Description
Recently, the tracking and documentation scripts broke which caused 3 separate merges to fix #3516 #3517 #3518. It is apparent we should probably have tests for these scripts, at least on the CI.
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 identifying the tracking and documentation scripts involved in fixes #3516, #3517, and #3518, then inspect the existing CI configuration. Done means the scripts have tests that run successfully in CI and would catch the failures that led to those merges.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100