istanbul - Yet another JS code coverage tool that computes statement, line, function and branch coverage with module loader hooks to transparently add coverage when running tests

  •        154

Deprecation Notice: this version of istanbul is deprecated, we will not be landing pull requests or releasing new versions. But don't worry, the Istanbul 2.0 API is now available and is being actively developed in the new istanbuljs organization. The best way to see it in action is to run node unit tests. Say you have a test script test.js that runs all tests for your node project without coverage.

https://github.com/gotwarlost/istanbul

Dependencies:

abbrev : 1.0.x
async : 1.x
escodegen : 1.8.x
esprima : 2.7.x
glob : ^5.0.15
handlebars : ^4.0.1
js-yaml : 3.x
mkdirp : 0.5.x
nopt : 3.x
once : 1.x
resolve : 1.1.x
supports-color : ^3.1.0
which : ^1.1.1
wordwrap : ^1.0.0

Tags
Implementation
License
Platform

   




Related Projects

isparta - A code coverage tool for ES6 (babel/6to5)

  •    Javascript

Isparta is a code coverage tool for ES6 using babel. Its intention is to be used with karma and karma-coverage, which provides code coverage reports using istanbul.

learn-istanbul - :checkered_flag: Learn how to use the Istanbul JavaScript Code Coverage Tool

  •    Javascript

Learn how to use Istanbul to check/track Code Coverage in your JavaScript projects. Like the road sign that is "Not In Use" too much code being written never gets executed.

simplecov - Code coverage for Ruby 1

  •    Ruby

SimpleCov is a code coverage analysis tool for Ruby. It uses Ruby's built-in Coverage library to gather code coverage data, but makes processing its results much easier by providing a clean API to filter, group, merge, format, and display those results, giving you a complete code coverage suite that can be set up with just a couple lines of code. In most cases, you'll want overall coverage results for your projects, including all types of tests, Cucumber features, etc. SimpleCov automatically takes care of this by caching and merging results when generating reports, so your report actually includes coverage across your test suites and thereby gives you a better picture of blank spots.

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 ...


coverage-ext - Generate code coverage for any webpage

  •    Javascript

This is an extension to an old version of chrome + a custom istanbul reporter. This combo gives you the power to view what JS gets evaluated on any website.

coverlet - Cross platform code coverage tool for .NET Core

  •    CSharp

Coverlet is a cross platform code coverage library for .NET Core, with support for line, branch and method coverage. Coverlet can be used either as a .NET Core global tool that can be invoked from a terminal or as a NuGet package that integrates with the MSBuild system of your test project.

EclEmma - Java Code Coverage for Eclipse

  •    Java

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.

EMMA Java code coverage tool

  •    Java

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.

test262 - Official ECMAScript Conformance Test Suite

  •    Javascript

Test262 itself is described in ECMA TR/104 and is included in ECMA-414 (pdf). The goal of Test262 is to provide test material that covers every observable behavior specified in the ECMA-414 Standards Suite. Development of Test262 is an on-going process. As of October 2017, Test262 consisted of over 29272 individual test files covering the majority of the pseudo-code algorithms and grammar productions defined in the ECMA-414 Standards Suite. Each of these files contains one or more distinct test cases. This marks the most comprehensive ECMAScript test suite to date. While test coverage is broad, TC39 does not consider coverage to be complete and as with any software project there exists the possibility of omissions and errors. This project welcomes any contributions to Test262 that help make test coverage of existing features more comprehensive.

XtCover

  •    DotNet

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.

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

xcov - Nice code coverage reporting without hassle

  •    Ruby

xcov is a friendly visualizer for Xcode's code coverage files. You can easily ignore the coverage for a specified set of files by adding their filenames to the ignore file specified with the --ignore_file_path parameter (this file is .xcovignore by default). You can also specify a wildcard expression for matching a group of files.

xcov - Nice code coverage reporting without hassle

  •    Ruby

xcov is a friendly visualizer for Xcode's code coverage files. You can easily ignore the coverage for a specified set of files by adding their filenames to the ignore file specified with the --ignore_file_path parameter (this file is .xcovignore by default). You can also specify a wildcard expression for matching a group of files.

tarpaulin - A code coverage tool for Rust projects

  •    Rust

Tarpaulin is designed to be a code coverage reporting tool for the Cargo build system, named for a waterproof cloth used to cover cargo on a ship. Currently, tarpaulin provides working line coverage but is still in the early development stage and therefore may contain some bugs. A lot of work has been done to get it working on some example projects and smaller crates so please report anything you find that's wrong. Also, check out our roadmap for planned features. Tarpaulin only supports x86_64 processors running Linux. This is because instrumenting breakpoints into executables and tracing their execution requires processor and OS specific code. It is a goal when greater stability is reached to add wider system support, however this is sufficient to run Tarpaulin on popular CI tools like Travis.

node-coveralls - lcov posting to coveralls.io

  •    Javascript

Coveralls.io support for node.js. Get the great coverage reporting of coveralls.io and add a cool coverage button ( like the one above ) to your README. This script ( bin/coveralls.js ) can take standard input from any tool that emits the lcov data format (including mocha's LCov reporter) and send it to coveralls.io to report your code coverage there.

flow-coverage-report - Generate flow coverage reports in JSON, HTML and in the console.

  •    Javascript

flow-coverage-report is a node command line tool to help projects which are using flow types in their JavaScript code to keep track and visualize the coverage of the flow types checks.

OpenCover

  •    

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