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

chai-tbd

v0.1.0

Published

An extension for chai to create failing *to be done* tasks.

Downloads

113

Readme

Build Status Coverage Status Dependency Status devDependency Status stable
NPM

chai-tbd

An extension for chai to create failing to be done tasks.

Installation

  • You need to have npm installed.
  • Use
    • npm install chai-tbd to retrieve the module or
    • npm install chai-tbd -D to save the developer dependency to your package.json.

Guide

When defining tests, I often start to write down the stubs for the tests I will have to implement. When finished I start to fill them with life. My problem was, what to do with those tests that have to be done.

With mocha you are able to simply leave the function out of the it command to mark it as pending.

describe('incomplete feature', function() {
  it('misses tests');
});

That's good, but actually, I wanted my tests to fail with a message.

So chai has the fail expression, to... well, to fail. So I could use that one. A little bit of a problem is, that its purpose is the use in custom validations. This is the reason, why the signature is not that handy.

describe('incomplete feature', function() {
  it('misses tests', function() {
    expect.fail('foo', 'bar', 'To be done!');
  });
});

Ok, you could also use null instead of 'foo' and 'bar', but that does not make it much nicer.

Long story short, I wrote this module to handle this situation.

var tbd = require('chai-tbd');

describe('incomplete feature', function() {
  it('misses tests', function() {
    tbd();
  });
});

You will have a clean stacktrace in your output:

  1) incomplete feature:
     AssertionError: To be done!
      at Context.<anonymous> (test/index.js:5:5)

If you want a special message in some cases, you can hand it over as an argument.

describe('incomplete feature', function() {
  it('misses tests', function() {
    tbd('I will implement this later');
  });
});

And if you don't like the common message "To be done!", you can configure it as well at retrieval time.

var notImplemented = require('chai-tbd').complain('Not implemented yet');

describe('incomplete feature', function() {
  it('misses tests', function() {
    notImplemented();
  });
});

API

tbd([message])

When called, this function throws an chai.AssertionError with the message "To be done!". The optional message param can be used to change the reason.
Note, that you can create a function with a permanent message, using tbd.complain(message).

tbd.complain(message)

This will return a function, that throws an chai.AssertionError with the given message. The returned function behaves exactly like tbd([message]) except, that its default reason is the message given.

License

MIT