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

cashmere

v0.4.9

Published

A javascript testing library

Downloads

6

Readme

cashmere

A javascript testing library.

Warning: Install at your own peril! This project is brand new and nowhere near ready!

Important: All test files must end in .test.js, the runner executes a find command with that extension

Note: As specified in engines, Node >=6.4.0 is required as ES6 Proxies are currently being used

Note: If you run the tests for cashmere, some of them fail intentionally to show FAIL output

To install:

yarn add cashmere or npm install cashmere

Here is an example of a test person.test.js:

describe('person', () => {
  context('#firstName()', () => {
    it('Should get first name', () => {
      expect({ hello: 'world' }).to.deep.equal({ hello: 'world' });
    });

    it('Should get middle name', () => {
      expect(1).to.equal(1);
    });
  });
});

Note that you don't have to import anything, including expect.

Here is an example of an asynchronous test websites.test.js:

describe('websites', () => {
  it.async('Facebook', (done, request) => {
    request.get('https://www.facebook.com', (err, res) => {
      expect(err).to.equal(null);
      expect(res.statusCode).to.equal(200);
      done();
    });
  });

  it.async('Halis Technology', (done, request) => {
    request.get('https://www.halistechnology.com', (err, res) => {
      expect(err).to.equal(null);
      expect(res.statusCode).to.equal(200);
      done();
    });
  });
});

For async tests it's it.async instead of it. Note that you don't have to import anything, including request.

Current Features

  • Unit tests
  • Mocha style describe/context/it
  • Async tests (brand new so use at your own peril)
  • Automatically compiles tests written in ES6
  • No special unicode characters in test output that don't display correctly in CI servers
  • No hiding logging statements
  • Clean stack traces
  • Diff output

Future Goals

  • Performance (may need parallel runs at some point)
  • Setup a global Redux-like store and have access to it from every test
  • Experiment with different testing styles
  • Probably need to store the output of asynchronous tests until done is called and then flush it all to the console at once

Note: In the tests you DO NOT need to import the following:

  • describe
  • context
  • it
  • expect
  • request
  • By
  • until

These are provided for you by default.

If you are using ESLint then put the following in your .eslintrc:

  "globals": {
    "expect": true
  },
  "env": {
    "mocha": true
  }

Note: This all works on Mac right now, Windows support could be added at some point