EclEmma vs Microsoft Code Coverage

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.

Microsoft Code Coverage measures how much of a project’s code is exercised by coded tests, such as unit tests. Its documented workflows cover.NET test projects with `dotnet test` and other.NET applications with the `dotnet-coverage` tool. It analyzes managed CLR and unmanaged native code using static or dynamic instrumentation; native coverage is disabled by default in the MTP extension. With Microsoft.Testing.Platform.MSBuild, extensions are auto-registered with MSTest, NUnit, and xUnit runners. The MTP extension can produce coverage, XML, and Cobertura reports, with settings for output, inclusion and exclusion rules, and instrumentation. It runs on Windows, macOS, and multiple Linux distributions, though instrumentation support varies by OS, version, and architecture. Other operating systems are supported on a best-effort basis, and some combinations allow static instrumentation only. Dynamic instrumentation on macOS and Linux requires libxml2, and missing dependencies may leave a report empty. MTP also excludes test assemblies by default unless configured otherwise. The plan is free.