Coveralls vs EclEmma

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.

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.