BullseyeCoverage vs Kover
BullseyeCoverage
bullseye.comKover
kotlin.github.ioSide by side
| Figure | BullseyeCoverage | Kover |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | Yes | — |
| Open source | — | — |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | Yes |
| Self-hosted | Yes | — |
| Plans published | 2 | 1 |
| Spec score · Test Coverage Tools | 8.5 (#4) | 7.4 (#19) |
| Instrumentation | BullseyeCoverage instruments source code and works with C++ and C code. | The Gradle plugin instruments classes as they are loaded into the JVM during tests, which may reduce performance or affect concurrent tests. |
| Language support | It supports standard versions of C++ from C++98 and C from C90 through the latest versions, plus compiler extensions. | The Gradle plugin supports mixed Kotlin and Java sources and can use JaCoCo as an alternative for coverage measurement and report generation. |
| Purpose | BullseyeCoverage measures C and C++ code coverage to help find untested code and assess testing completeness. | Kover is a set of tools for collecting test coverage of Kotlin code compiled for JVM and Android platforms. |
| Reports | Coverage can be viewed interactively in Coverage Browser or generated as HTML or console reports. | The Gradle plugin generates HTML and XML coverage reports and supports coverage verification rules. |
| Support | The company says technical support is included with every purchase and provides a technical support request form. | The repository links to contributing guidelines and a code of conduct. |
Plans
BullseyeCoverage
- Evaluation licenseFree
- BullseyeCoverage licensePrice not published
In their own words
BullseyeCoverage
BullseyeCoverage measures C and C++ code coverage to help developers and testers locate untested code and assess testing completeness. It provides function coverage and condition/decision coverage, and results can be viewed interactively in Coverage Browser or generated as reports. Listed outputs include HTML, text, annotated source code, XML, Cobertura, and CSV. The tool instruments C and C++ source code and supports standard C++ versions from C++98 and C versions from C90 through current versions, plus compiler extensions. Coverage data can be exported in XML or CSV, and results from multiple computers can be merged. Supported tools include Visual Studio, Clang, GCC, Xcode, CMake, Eclipse, and embedded development tools such as Code Composer Studio. Supported environments include Windows, Linux desktop and server, macOS, and embedded systems. The company reports that instrumented execution takes 1.3–1.9× longer and code and data size increase to 1.4×; build-time effects vary by compiler. A temporary, fully functional evaluation license costs nothing and expires at the end of its evaluation period. The perpetual paid license has no listed price.
Kover
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.