Displaying 1 to 20 from 44 results

angular-starter - :tada: An Angular Starter kit featuring Angular (Router, Http, Forms, Services, Tests, E2E, Dev/Prod, HMR, Async/Lazy Routes, AoT via ngc), Karma, Protractor, Jasmine, Istanbul, TypeScript, TsLint, Codelyzer, Hot Module Replacement, @types, and Webpack by @TipeIO

An Angular starter kit featuring Angular 5, Ahead of Time Compile, Router, Forms, Http, Services, Tests, E2E), Karma, Protractor, Jasmine, Istanbul, TypeScript, @types, TsLint, Codelyzer, Hot Module Replacement, and Webpack by AngularClass.This seed repo serves as an Angular starter for anyone looking to get up and running with Angular and TypeScript fast. Using a Webpack 3 for building our files and assisting with boilerplate. We're also using Protractor for our end-to-end story and Karma for our unit tests.

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

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.

c8 - collect test coverage using v8's inspector

Code-coverage using v8's Inspector that's compatible with Istanbul's reporters.The above example will collect coverage for foo.js using v8's inspector.

v8-to-istanbul - convert from v8 coverage format to istanbul's format

converts from v8 coverage format to istanbul's coverage format.

gulp-istanbul - Istanbul unit test coverage plugin for gulp.

Istanbul unit test coverage plugin for gulp.Works on top of any Node.js unit test framework.

web-component-tester-istanbul - Instanbul coverage reporting for projects being tested by web-component-tester

Istanbul coverage plugin for web-component-tester. Use this plugin to collect and report test coverage (via istanbul) for your project on each test run.

remap-istanbul - A tool for remapping Istanbul coverage via Source Maps

A package that provides the ability to remap Istanbul code coverage information to its original source positions based on a JavaScript Source Maps v3. remap-istanbul requires NodeJS 6 or later.

istanbul-cobertura-badger - Create a Code Coverage badge for Node.js Apps running node-istanbul.

Creates a coverage badge by reading the Cobertura XML coverage report from node-istanbul reports using https://github.com/badges/shields. The idea is to serve in the Node.js README for internal use in a GitHub enterprise machine along with Jenkins.

FE-CI - Front End Testing and Continuous Integration

This repo demonstrates how to start a new project using best Test Driven Development techniques plus a CI workflow with code coverage support. The technologies, services and libraries used in this repo is CoffeeScript, Grunt, Jasmine, Karma, IstanbulJS, Coveralls and Travis. The blog post currently in Turkish but I am planning to post another one in English soon.

istanbul-react - Instrumenter for 1:1 mapping of React JSX components

You can use modifyCodeBeforeInstrumentation to modify code before instrumentation. It might be useful for example to get around chrome bug with 'use strict';. It takes one argument, which give you an object, with two properties code - original code, filename - name of the file. This callback must return modified code as a string. In the example below you can see how 'use strict'; is prefixed with semi-colon to work around bug (or feature?) in chrome.

grunt-istanbul - JavaScript codecoverage tool for Grunt

You can also pass an instrumenter argument to the instrument options as well as any other arguments that your instrumenter takes.

grunt-jasmine-node-coverage - Grunt task for running jasmine-node

A Grunt task to run your Jasmine feature suite using jasmine-npm and Istanbul for code coverage reports. The minimum supported Node.js version is 4.2.0 (LTS), and while works also in 0.10.x, no quarantees are given.

grunt-istanbul-coverage - Grunt plugin to enforce coverage thresholds from istanbul coverage JSON files

I wanted more than just insight into code coverage but a way to enforce threshold limits as well. TIP: I suggest you clean the coverage folder each time to speed up the checks and so you're only validating the most recent coverage levels.