npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

jest-coverage-partial-compare

v1.1.3

Published

Compares the summary-coverage.json files between two branches

Downloads

15

Readme

jest-coverage-partial-comparison

This is a fork from https://github.com/jschaftenaar/jest-code-coverage-protection, the fundamental difference is that it compares each file from the report instead of the summarized total. This means it supports the "changedSince" option present in Jest configuration, now we don;t need to run the entire test suite in order to compare the coverage to the a previous state.

Requirements

  • Add json-summary as coverage reporter to jest configuration

Install

npm install jest-coverage-partial-comparison --save-dev

Add the command to package.json

  "scripts": {
    "jcpc": "jcpc"
  },

usage options

Usage: jcpc [options]

Compare coverage-summary.json generated by jest (including the "changedSince: variation)

Options:
  -V, --version              output the version number
  -f, --file <filename>      The file generated by the (feature) branch you want to check (default: "coverage/coverage-summary.json")
  -c, --compare <filename>   The file generate by the (master) branch you want to compare against (default: "master/coverage/coverage-summary.json")
  -n, --new <threshold       The minimal threshold new code should have (default: "0.80")
  -v, --variance <variance>  Allow for variance, e.g. allow 0.05 to allow a 5% decrease using hold (default: "0")
  -h, --help                 display help for command

Configure ci/cd:

  • Make sure your branches generate the coverage-summary.json file using the coverage reporter json summary
  • Add checkout of comparison branch(master) to your build step
  • Run jcpc command
  • Catch exit codes of jcpc, 0 = coverage check passed, 1 = coverage check failed

Examples

jcpc -n 0.9   <new code should have at least 90% code coverage>
jcpc  -v 0.5  <overall code coverage should be within 0.5% of comparison branch>
jcpc -f cover.json   <specify input file for the feature branch>