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

hubot-harness

v1.0.1

Published

Test harness for Hubot script and plugin development

Downloads

30

Readme

hubot-harness

npm | Node CI

This is a testing harness for Hubot scripts and packages that takes advantage of language features like async/await, with support for interactions across multiple rooms and users.

Installation

Hubot 3.x is a peer dependency, so your package will also need to depend on Hubot itself separately. If you're writing Hubot scripts, this is likely already the case.

npm install --dev hubot-harness

Use

Here's an example using a Mocha test suite. Note that there isn't anything Mocha-specific in the test harness.

const {Harness} = require("hubot-harness");

describe("my command", function () {
  let hubot;

  beforeEach(function () {
    hubot = new Harness({name: "the-bot"});

    // Use .load() to initialize this bot with the scripts you wish to test.
    // Its arguments are combined with `path.resolve()`.
    hubot.load(__dirname, "../scripts/my-script");
  });

  it("runs a command and waits for the response", async function () {
    hubot.say("the-bot: ping");
    await hubot.waitForResponse("PONG");
  });

  it("can match responses with regular expressions", async function () {
    hubot.say("the-bot: do the thing");
    await hubot.waitForResponse(/the thing is complete/);
  });

  it("can say things as different users", async function () {
    hubot.createUser("id0", "user-zero");
    hubot.createUser("id1", "user-one", {extra: true});

    hubot.sayAs("id0", "can i do this");
    await hubot.waitForResponse(/no/);

    hubot.sayAs("id1", "can i do this");
    await hubot.waitForResponse(/yes/);
  });

  it("can say and listen in different rooms", async function () {
    const room0 = hubot.createRoom("#zero");
    const room1 = hubot.createRoom("#one");

    room0.say("which room is this");
    await room0.waitForResponse(/#zero/);

    room1.say("which room is this");
    await room1.waitForResponse(/#one/);
  });
});