EclEmma
eclemma.org
What it is
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.
Spec sheet
- Purpose
- EclEmma is a Java code coverage tool that brings coverage analysis into the Eclipse workbench.Read 7 Oct 2026 · eclemma.org
- Intended users
- The Eclipse integration focuses on supporting individual developers; the site points users to JaCoCo integrations for automated builds.Read 7 Oct 2026 · eclemma.org
- Integrations
- EclEmma is based on JaCoCo and is available through the Eclipse Marketplace Client, an update site, or manual installation.Read 7 Oct 2026 · eclemma.org
- Support
- The project directs users to its documentation and FAQ, then to the JaCoCo and EclEmma Users group; bugs can be reported through the Eclipse issue tracker.Read 7 Oct 2026 · eclemma.org
- License
- The program is provided under the Eclipse Public License 2.0.Read 7 Oct 2026 · eclemma.org
- Founded
- 2006Read 28 Sep 2026 · eclemma.org
- Coverage analysis
- The Coverage view summarizes coverage by Java project and allows drill-down to method level, while source editors highlight covered and uncovered code.Read 7 Oct 2026 · eclemma.org
- Coverage counters
- Coverage summaries can use instruction, branch, line, method, type, and cyclomatic complexity counters.Read 7 Oct 2026 · eclemma.org
- Import and export
- EclEmma imports JaCoCo .exec execution data and exports coverage reports in HTML, XML, or CSV, as well as JaCoCo execution data files.Read 7 Oct 2026 · eclemma.org
- Launch types
- Coverage mode supports local Java applications, Eclipse/RCP applications, Equinox OSGi, JUnit, TestNG, JUnit plug-in tests, JUnit RAP tests, SWTBot tests, and Scala applications.Read 7 Oct 2026 · eclemma.org
- Release integrity
- The download page lists MD5 and SHA-256 checksums for releases.Read 7 Oct 2026 · eclemma.org
- Requirements and OS
- The installation page requires Eclipse 3.8 or higher and Java 1.5 or higher, says there is no dependency on a particular operating system, and requires Eclipse Java development tools.Read 7 Oct 2026 · eclemma.org
- Sessions
- Users can switch between multiple coverage sessions and merge sessions from different test runs.Read 7 Oct 2026 · eclemma.org
Plans and prices
Strong points and limits
Strong points
- Coverage can be inspected down to method level.
- Supports six coverage counters.
- Can merge sessions from different test runs.
- Exports HTML, XML and CSV reports.
- Has no stated operating-system dependency.
Limits
- Requires Eclipse 3.8 or higher.
- Requires Java 1.5 or higher.
- Requires Eclipse Java development tools.
- Eclipse integration focuses on individual developers.
Who it suits
EclEmma suits individual developers using Eclipse who want coverage views and reports for Java or Scala work. The project points users seeking automated-build integration toward JaCoCo integrations.
Verdict
EclEmma provides coverage analysis within Eclipse, including session management and report export. Its requirements are tied to Eclipse and Java, and its integration focus is individual development rather than automated builds.
Where Specifiction places it
- Test Coverage Tools#9 of 277.8