mapillary / mapillary/mapillary-python-sdk
[Good First Issue, Discussion] Code Coverage Measure
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 66
- Forks
- 23
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 11
Description
Complimentary of #103, we would need some way of showcasing the code coverage within the project to assess how many of the functionalities have been tested.
There is nothing decided right now on what to use, but the GitHub Marketplace has some interesting add-ons, such as CodeCov, that can be integrated into the project.
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 issue #103 and the repository's existing test setup; this issue names no files, tests, or entry points. Compare the GitHub Marketplace coverage options mentioned, then define an integration whose completed state visibly reports how much project functionality is tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, python
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100