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

v2.0.1

Published

Check for inflated coverage due to un-mocked dependencies

Downloads

20

Readme

jest-enforce

Are you mocking me?

When you run your unit tests, what does your dependency tree look like? Are your unit tests pulling in the actual dependencies of your modules, thereby making them brittle?

Use jest-enforce to ensure you're mocking all of your dependencies.

Install

npm intall --save-dev jest-enforce

Use

jest-enforce <regexForTestFiles>

Functionality

The command line util calls jest <regexForTestFiles> --listTests, which lists all of the applicable test files to be run. It then runs each of these tests (synchronously, for now) using your jest configuration in package.json (if applicable) and collects their coverage reports. If the coverage report includes files that are not whitelisted for coverage, jest-enforce will warn you via console print out.

NOTE: If ANY of your tests fail, jest-enforce will as well. All tests must pass in order for this tool to catch extraneous coverage.

Configuration

You can add a configuration to your package.json file. Here's an example:

"jest-enforce": {
  "whitelist": ["sourceOfTruth.js$", "src/js/config/**/*.jsx"],
  "printList": true,
  "testNameFormat": "(\\.spec|\\.test)"
}

Keep in mind that JSON does not support regex, so these strings are converted when jest-enforce is called. Regular expression operators like \w need to be escaped: \\w.

Options

whitelist: ["<regularExpression>",...]

If a file path matches one of the expressions in the whitelist it will be excluded from warnings.

printList: <true/false>

Print the full list of files getting extraneous coverage. Default is true.

testNameFormat: "<regularExpression>"

The format in which your test files are named. This removes a portion of the test file path to match the file path it's testing. For example: example.spec.js -> example.js. As mentioned above, JSON does not support regex, so regular expression operators must be escaped. Default assumes the only difference is .spec or .test: "(\\.spec|\\.test)(.\\w+$)".

TODO:

  • [ ] Determine performance bottlenecks
  • [ ] Whitelist for specific files
  • [ ] Add option for silent mode