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

baseline-tester

v1.1.1

Published

Runs a function against given inputs and tests the result against baseline outputs

Downloads

12

Readme

Test a function against baseline output

Let's say you're writing a function that transforms some text into some other text. This package makes testing such a function easy, by letting you set up source files alongside their corresponding desired baseline output files, and then seeing if your function generates the right results.

Example

Let's say you're writing a Markdown-to-HTML converter, and have set up your project like so:

lib/
  md2html.js
test/
  cases/
    bold.md
    bold.html
    paragraphs.md
    paragraphs.html
    ⋮

Here we assume lib/md2html.js has a default export that is a function converting strings of Markdown to strings of HTML, synchronously.

To run the tests using baseline-tester, you can either use the CLI:

$ baseline-tester lib/md2html.js --cases test/cases --input md --output html

or you can do so programmatically (say, from test/runner.js):

"use strict";
var path = require("path");
var baselineTester = require("baseline-tester");
var md2html = require("../lib/md2html.js");

baselineTester(md2html, {
    casesDirectory: path.resolve(__dirname, "cases"),
    inputExtension: "md",
    outputExtension: "html"
});

Trimming

It's common to want to ignore leading or trailing whitespace when comparing against the baseline files. baseline-tester will do this by default, but you can turn it off by specifying --trim=none on the command line or trim: "none" programmatically.

Testing Exceptions

If you want to test that your function throws certain exceptions, you can use a slightly modified setup. On the command line, pass the additional option --exceptions; when used programmatically, pass the additional option checkExceptions: true.

For example, if you stored your exceptional cases under test/exceptions with the exception messages being given extension .txt, you could do

$ baseline-tester lib/md2html.js --exceptions --cases test/exceptions --input md --output txt

Exception messages are checked against the message: i.e., are the contents of the "output" file equal to the exception's message property (modulo potential trimming).