Coveralls vs Kover

Coveralls analyzes software test coverage, showing teams which code is not covered by tests. Its dashboard presents project coverage percentages and their changes over time, while repository views drill down from a project to sub-projects, files, and individual lines. Build history tracks coverage across branches, including pull requests. Coveralls can add summarized coverage results to pull requests and send status updates that apply coverage criteria to merge decisions. Notifications can go to Slack or webhooks. It supports line and branch coverage, with report formats including LCOV, SimpleCov, Cobertura, JaCoCo, and Clover XML. Coveralls says it works with any CI service and lists more than 30 community-created integrations, a GitHub Action, and a CircleCI Orb. An API can add repositories programmatically and return recent build statistics. Open-source and public repositories are free. The Starter plan is $10 a month for one private repository and includes a 30-day trial. A self-hosted enterprise installation can operate within existing security controls without outbound network access.

Kover is a free, Apache-2.0-licensed toolkit maintained by Kotlin for measuring test coverage in Kotlin and Java code compiled for JVM and Android targets. It provides Gradle and Maven plugins, a command-line interface, offline instrumentation, a JVM agent, and a features artifact. The Gradle plugin creates HTML and XML reports, supports IC output, and can enforce coverage gates using line, instruction, and branch measurements. It integrates with Kotlin JVM, Kotlin Android, Kotlin Multiplatform, and the com.android.kotlin.multiplatform.library plugins, including mixed Kotlin and Java sources. JaCoCo can replace Kover for measurement and report generation. Android build variants and Android host tests are supported, but instrumented tests on devices are not collected. JavaScript and native targets are outside the Gradle plugin’s support. Requirements include Gradle 6.8.3 or later, JVM 1.7 or later for tests, and Android Gradle Plugin 7.0.0 or later. Class instrumentation during JVM test loading may affect performance or concurrent tests.