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

it-fails

v1.0.7

Published

[![Build Status](https://travis-ci.org/mlrawlings/it-fails.svg?branch=master)](https://travis-ci.org/mlrawlings/it-fails)

Downloads

92

Readme

it.fails() - allow failing mocha tests

Build Status

npm install --save-dev it-fails

image

Why

Similar to in ava, you can use the .fails modifier to document issues with your code that need to be fixed. Failing tests are run just like normal ones, but they are expected to fail, and will not break your build when they do. If a test marked as failing actually passes, it will be reported as an error and fail the build. Once a test is passing you can should remove the .fails modifier.

This allows you to merge failing tests before a fix is implemented without breaking CI. This is a great way to recognize good bug report PR's with a commit credit, even if the reporter is unable to actually fix the problem.

Usage

Require the module, then use it.fails like you would it.only or it.skip.

require('it-fails');

it.fails('a test that will fail', function() {
    throw new Error('oops')
});

Additional features

The base reporter's epilogue is also overwritten by this module to show a summary that is aware of expected failures. The epilogue now shows skipped tests in addition to failures.

You can optionally set test.details (test is returned from it), which will display additional text when the test is printed out. This can be used to display an issue associated with a failing test or the reason for a test being skipped.

Demo

Run npm run demo to see the output from the screenshot above. Also check out npm run demo2 and npm run demo3.