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

testing-steps

v1.0.8

Published

An acceptance testing language organized as an ordered list of steps.

Downloads

9

Readme

Testing steps

An acceptance testing language organized as an ordered list of steps.

This alternative to BDD allows you to specify your tests as simple numbered lists of testing steps. A template system allows you to define parameterized functions which will run your steps.

Installation

npm install testing-steps --save-dev

Usage

First, you need to define your steps. You can do this by calling defineStep, passing a template string for matching with steps along with a function that will execute a given step.

import { defineStep } from "testing-steps";

class Adder {
  sum = 0;

  add(first, second) {
    console.log("Add called.");
    this.sum = first + second;
  }
}

const adder = new Adder();

defineStep("add {first} and {second}", ({ first, second }) => {
  adder.add(parseInt(first), parseInt(second));
});

defineStep("observe that sum is {expectedSum}", ({ expectedSum }) => {
  expect(adder.sum).toEqual(parseInt(expectedSum));
});

Now that your steps are defined, you can run them by calling runSteps.

describe("adder", () => {
  test(`
    1. Add 2 and 3
    2. Observe that sum is 5
  `, () => {
    runSteps();
  });
});

This will parse the steps listed in the test string and call the defined test functions with the appropriate parameters.

API

defineStep(template, fn)

Creates a step definition, which consists of a template (used to match it with a step) and a function (which executes on the step being reached).

template

String with template with parameter names, each wrapped in curly braces. The template is case-insensitive, except for the parameter names, which are case-sensitive.

Example: add {firstNumber} and {secondNumber}

fn

Function which runs when a step is matched with {template}. The values matching the parameter places defined in the {template} are passed to {fn} as named properties of the first parameter.

Example: function ({ firstNumber, secondNumber }) { }.

runSteps()

Runs the steps defined in the test name.

Intended to be used within a test or it block in a Jest or Jasmine test.