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

@virtuous/unit-tests

v2.1.0

Published

Virtuous' unit test suite using Jest and Enzyme.

Downloads

5

Readme

Virtuous' Unit Test Suite

Build Status Coverage Status GitHub (pre-)release License

This configuration uses Jest for running the tests. It is only an extension of the default Jest configuration.

Installation

NPM

npm install --save-dev @virtuous/unit-tests

Yarn

yarn add --dev @virtuous/unit-tests

Usage

All test files should follow the naming convention of *(spec|test).js. But that is not mandatory. You can also put your test files into one or multiple __tests__ folder(s).

NOTE: It is considered a best practice to create __tests__ folder(s) AND have the file endings like *.spec.js or *.test.js!

Test Setup

You have two options of how to create a configuration for Jest:

  • You can create your own configuration following the Jest Documentation
  • You can use Virtuous' pre-defined configuration and extend it as you wish.

NOTE: Using and extending the Virtuous configuration is the preferred way!

1. Using Virtuous' configuration

Create a file called jest.config.js in the root of your project. Add the following line to it:

module.exports = require('@virtuous/unit-tests/jest.config');

2. Extending Virtuous' configuration

Create a file called jest.config.js in the root of your project. Add the following line in the beginning of the file:

const defaultConfig = require('@virtuous/unit-tests/jest.config');

This will load the default configuration. Now you can extend it by spreading the defaultConfig into a newly created configuration object:

module.exports = Object.assign({}, defaultConfig, {}
  [Your config goes here],
});

Example Configuration

Here is an example showing how to extend the default configuration:

const defaultConfig = require('@virtuous/unit-tests/jest.config');

module.exports = Object.assign({}, defaultConfig, {
  moduleNameMapper: {
    '^Components(.*)$': '<rootDir>/components',
    '^Styles(.*)$': '<rootDir>/styles',
  },
});