•        158

It stands for eXTreme COVERage, a web based .NET code coverage reporting tool on top of VS CoveragAPIs. It provides the coverage summary in an enhanced way what VS tools does not Provide.




Related Projects

griffon-clover-plugin - Code coverage with Clover for Griffon projects

Code coverage with Clover for Griffon projects

gradle-clover-plugin - Gradle plugin for generating a code coverage report using Clover

Gradle plugin for generating a code coverage report using Clover

VSTS Code Coverage Runner - Get VS Code Coverage from NUnit or MbUnit

This project is an attempt to provide a wrapper around the VSTS instrumentation and code coverage tools. VSTS provides very powerful code coverage tools with Visual Studio, but as packaged, you need to be running MSTest unit tests to obtain this coverage data. There is a way ...

EclEmma - Java Code Coverage for Eclipse

EclEmma is a free Java code coverage tool for Eclipse, available under the Eclipse Public License. It brings code coverage analysis directly into the Eclipse workbench. The EclEmma project is also the home of the JaCoCo code coverage library which is the technical back-end for EclEmma and also has integrations with many other build and software quality tools.

devel-cover-report-clover - Backend for Atlassian Clover reporting of coverage statistics

Backend for Atlassian Clover reporting of coverage statistics

EMMA Java code coverage tool

EMMA is an open-source toolkit for measuring and reporting Java code coverage. EMMA can instrument classes for coverage either offline (before they are loaded) or on the fly (using an instrumenting application classloader). The coverage stats are aggregated at method, class, package, and "all classes" levels. EMMA can instrument individial class files or entire jars.

phpunit-coverage-listener - Report code coverage statistics to third-party services

PHPUnit Coverage Listener is a utility library that allow you to process the PHPUnit code-coverage information and send it into some remote location via cURL.Above json data could be process furthermore to expose usefull information about your code-coverage information in a way that fit with your specific needs. Coveralls service would be a perfect example in this scenario.

intellij-coverage - IntelliJ IDEA code coverage agent

Apache 2 licensed code coverage engine for JVM. Supports branch coverage and per-test coverage tracking. Used in IntelliJ IDEA and in JetBrains TeamCity.Open the project directory as an IntelliJ IDEA project and run Build | Rebuild Project. The agent binary is created as "coverage-agent.jar" in the 'dist' directory.


Visual Studio coverage converter tool. Converts Visual Studio Coverage files (*.coverage) to clover or html format.

Bullseye Code Coverage XML Parser Tool

Bullseye Code Coverage XML Parser : Just browse for the coverage xml and enter the files you want to list coverage details for and voila , you get the no of functions covered , tot no of functions, coverage %. For more information just download and see Readme.txt

courtney - Courtney is a coverage tool for Go

Courtney makes your code coverage more meaningful, by excluding some of the less important parts.If you need to test that your code panics correctly, it should probably be an error rather than a panic.

Cobertura - Code coverage tool

Cobertura is a Java tool that calculates the percentage of code accessed by tests. It can be used to identify which parts of your Java program are lacking test coverage. it instruments Java bytecode after it has been compiled. Reports are generated in HTML and XML. It shows cyclomatic code complexity of each class, and the average cyclomatic code complexity for each package and for the overall product.


A code coverage tool for .NET 2 and above, support for 32 and 64 processes (including Silverlight) with both branch and sequence points.

gradle-docker-test-runner - Gradle plugin for running tests in Docker environments

This plugin provides a simple way to test Gradle projects in multiple different environments specified in Dockerfiles as part of a build. Given a set of Dockerfiles that contain the desired environments, this plugin adds tasks for running the project's tests and coverage tasks in those containers. The test and coverage output for each environment is persisted separately, and it is possible to combine the coverage from the tests run in all of the environments using gradle-jacoco-coverage.This plugin makes it trivial to test existing projects against multiple different environments in a lightweight manner. The ability to easily run tests in different environments locally makes the development process faster and allows environment verification to be part of the core build. It also allows code coverage to properly account for code that will only execute in certain environments.

nodejs-code-coverage-example - A code coverage example for node.js using Mocha and jscov

A code coverage example for node.js using Mocha and jscov

CC.NET-Code-Coverage-Extensions - Application and XSLT files for using code coverage metrics.

Application and XSLT files for using code coverage metrics.