build: measure code coverage by tests
Open
Nobody has claimed this yet.
build
maintenance
- Dominant language
- Go
- Stars
- 59.8k
- Forks
- 5.4k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 48
Description
rclone has grown to a pretty complex project. I propose to use a tool like coverall to estimate the effect of patches on the test-ability.
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
No files, tests, or CI entry points are named. Start by reviewing the repository's build and CI configuration and investigate Go coverage reporting with Coveralls or a similar tool; done means patches produce a usable test-coverage measurement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- 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