All Projects → istanbuljs → Istanbuljs

istanbuljs / Istanbuljs

monorepo containing the various nuts and bolts that facilitate istanbul.js test instrumentation

Programming Languages

javascript
184084 projects - #8 most used programming language

Projects that are alternatives of or similar to Istanbuljs

Baretest
An extremely fast and simple JavaScript test runner.
Stars: ✭ 364 (-44.51%)
Mutual labels:  jest, mocha, tap
tropic
🍍 Test Runner Library
Stars: ✭ 29 (-95.58%)
Mutual labels:  tap, mocha, jest
eslint-config-adjunct
A reasonable collection of plugins to use alongside your main esLint configuration
Stars: ✭ 39 (-94.05%)
Mutual labels:  mocha, jest, ava
Jest Codemods
Codemods for migrating to Jest https://github.com/facebook/jest 👾
Stars: ✭ 731 (+11.43%)
Mutual labels:  jest, mocha, ava
awesome-javascript-testing
🔧 Awesome JavaScript testing resources
Stars: ✭ 28 (-95.73%)
Mutual labels:  mocha, jest, ava
Rxjs Marbles
An RxJS marble testing library for any test framework
Stars: ✭ 267 (-59.3%)
Mutual labels:  jest, mocha, ava
Public
Repository for wallaby.js questions and issues
Stars: ✭ 662 (+0.91%)
Mutual labels:  jest, mocha, ava
Redux Saga Testing
A no-brainer way of testing your Sagas
Stars: ✭ 150 (-77.13%)
Mutual labels:  jest, mocha, ava
Enzyme
JavaScript Testing utilities for React
Stars: ✭ 19,781 (+2915.4%)
Mutual labels:  jest, mocha, ava
qa-automation-base
There are basic projects for automation frameworks based on Kotlin/Java and TypeScript for the backend, frontend, and mobile.
Stars: ✭ 45 (-93.14%)
Mutual labels:  mocha, jest
wily
Build Node.js APIs from the command line (Dead Project 😵)
Stars: ✭ 14 (-97.87%)
Mutual labels:  mocha, jest
xv
❌ ✔️ zero-config test runner for simple projects
Stars: ✭ 588 (-10.37%)
Mutual labels:  mocha, jest
fixturez
Easily create and maintain test fixtures in the file system
Stars: ✭ 57 (-91.31%)
Mutual labels:  mocha, ava
titef
🌠 A tiny, lightning-fast, zero-dependecies JavaScript test framework 🌠
Stars: ✭ 19 (-97.1%)
Mutual labels:  mocha, ava
patent-free-react-ecosystem-migration-plan
Patent Free React Ecosystem Migration Plan
Stars: ✭ 15 (-97.71%)
Mutual labels:  mocha, jest
playwright-test
Run unit tests with several runners or benchmark inside real browsers with playwright.
Stars: ✭ 81 (-87.65%)
Mutual labels:  mocha, code-coverage
ts-snippet
A TypeScript snippet compiler for any test framework
Stars: ✭ 29 (-95.58%)
Mutual labels:  mocha, ava
react-multi-context
Manage multiple React 16 contexts with a single component.
Stars: ✭ 19 (-97.1%)
Mutual labels:  mocha, jest
react16-seed-with-apollo-graphql-scss-router4-ssr-tests-eslint-prettier-docker-webpack3-hot
Seed to create your own project using React with Apollo GraphQL client
Stars: ✭ 19 (-97.1%)
Mutual labels:  mocha, jest
Sazerac
Data-driven unit testing for Jasmine, Mocha, and Jest
Stars: ✭ 322 (-50.91%)
Mutual labels:  jest, mocha

IstanbulJS

Greenkeeper badge Build Status Coverage Status Conventional Commits community slack

Having problems? want to contribute? join our community slack.

Everyone's favorite JS code coverage tool.

About this Repo

This monorepo contains the nuts and bolts utility libraries that facilitate IstanbulJS test coverage; Why a monorepo?

  • it allows us to more easily test API changes across coupled modules, e.g., changes to istanbul-lib-coverage potentially have an effect on istanbul-lib-instrument.
  • it gives us a centralized repo for discussions about bugs and upcoming features.

Where Should I Start

You're probably actually looking for one of the following repos:

  • nyc: the IstanbulJS 2.0 command line interface, providing painless coverage support for most popular testing frameworks.
  • babel-plugin-istanbul: a babel plugin for instrumenting your ES2015+ code with Istanbul compatible coverage tracking.
  • istanbul: the legacy 1.0 IstanbulJS interface (you should now consider instead using nyc or babel-plugin-istanbul).

Contributing

Contributing to the packages contained in this repo is easy:

  1. after checking out, run npm install (this will run the lerna build).
  2. to run all tests, simply run npm test in the root directory.
  3. to run tests for a single package cd package/:name and run npm test within the package's folder.
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].