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

mochafe

v0.0.5

Published

Steps for Mocha

Downloads

11

Readme

Mochafe

Build Status Code Climate David DM

Mocha with steps.

Install

npm install mochafe --save-dev

Usage

var Mochafe = require("mochafe");

describe("Feature title", function() {
  var fe = new Mochafe();

  fe.steps("a > b", function(a, b) {
    assert(a > b);
  });

  fe.steps("b < c", function(b, c) {
    assert(b < c);
  });

  it("acts as a scenario title", function() {
    fe.step("a > b", 2, 1);
    fe.step("a > b", 3, 2);
    fe.step("b < c", 4, 5);
  });
});

Async steps are created by passing true as the first argument in the steps method. This will automatically append a next argument which you can call when your async process has finished.

next argument can be named whatever you want.

describe("Feature title", function() {
  var fe = new Mochafe();
  var start = Date.now();
  var stop;

  fe.steps(true, "will takes some time", function(a, b, c, next) {
    setTimeout(function() {
      assert.equal(a, "A");
      assert.equal(b, "B");
      assert.equal(c, "C");
      stop = Date.now();
      next();
    }, 1000);
  });

  fe.steps("has taken at least about a second", function() {
    assert(stop-start > 999);
  });

  it("acts as a scenario title", function(done) {
    fe.step("will takes some time", "A", "B", "C");
    fe.step("has taken at least about a second");
    fe.step(done);
  });
});

Steps can be saved in "global" export files and imported as required.

module.exports = {
  "I will use this step alot": function(a, b) {
    assert.equal(a, b);
  },
  "This one is async": [true, function(a, b) {
    assert(a > b);
  }]
}

var globalSteps = require("./global_steps");

var fe = new Mochafe({
  steps: [
    globalSteps
  ]
});

TODO

  • Set context (this) so steps are executed against said context.

License

MIT