Add code coverage tag other than build CI
Open
Nobody has claimed this yet.
- Dominant language
- Terra
- Stars
- 795
- Forks
- 175
- PR merge metrics
- No merged PRs in 30d
Description
Maybe consider coveralls? Looks like its plugin is a modification of JaCoCo optimized for envs like Travis CI with less memory consumption.
http://blog.eluder.org/2013/06/code-coverage-for-github-hosted-java-projects-with-coveralls
Contributor guide
No contributing guide indexed for this repository
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 repository's build CI configuration and the linked Coveralls proposal to identify how JaCoCo coverage is currently handled. Clarify which separate coverage integration is intended and what successful reporting, without disrupting the build, would look like.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100