EclEmma vs Kover

EclEmma is a Java code coverage tool that brings coverage analysis into the Eclipse workbench. It supports local Java applications, Eclipse and RCP applications, Equinox OSGi, JUnit, TestNG, Eclipse plug-in and RAP tests, SWTBot tests, and Scala applications. Its Coverage view summarizes results by project and lets developers inspect methods; source editors highlight covered and uncovered code. Coverage summaries can use instruction, branch, line, method, type and cyclomatic complexity counters. Users can switch among coverage sessions or merge results from separate test runs. EclEmma imports JaCoCo.exec data and exports reports in HTML, XML or CSV, as well as JaCoCo execution data files. It is based on JaCoCo and can be installed through the Eclipse Marketplace Client, an update site or manually. The free plug-in is listed at free under the Eclipse Public License 2.0. It requires Eclipse 3.8 or higher, Java 1.5 or higher, and Eclipse Java development tools; the project states that it has no operating-system dependency. Its Eclipse integration focuses on individual developers, with JaCoCo integrations suggested for automated builds.

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.