We currently use JaCoCo together with some actions that generate a check run and a comment for JaCoCo coverage.
We have no good way of generating a code coverage badge for the README.
We might want to switch to a dedicated service like "codecov", "codacy", or coveralls (this only supports LCOV which is a hassle to get right w/ Kotlin and Gradle).
We can consider this move after HumLib moved to a GitHub organization as this makes identifying us as an Open Source project easier. This is important for pricing of said services.
mor4thii
commented
2 years ago
We currently use JaCoCo together with some actions that generate a check run and a comment for JaCoCo coverage. We have no good way of generating a code coverage badge for the README.
We might want to switch to a dedicated service like "codecov", "codacy", or coveralls (this only supports LCOV which is a hassle to get right w/ Kotlin and Gradle).
We can consider this move after HumLib moved to a GitHub organization as this makes identifying us as an Open Source project easier. This is important for pricing of said services.