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

qunit-snapshot

v1.3.2

Published

A brand new TypeScript library.

Downloads

810

Readme

qunit-snapshot

Snapshot-based assertions for QUnit test suites

Build Status codecov Version

Setup

First, install this library in your project as a devDependency

yarn add -D qunit-snapshot

then, before running your tests, setup the plugin

import { setupSnapshots } from 'qunit-snapshot';

// It is your responsibility to implement these two functions
setupSnapshots(QUnit, {
  getSnapshot(
    moduleName?: string|undefined,
    testName: string,
    snapName: string) { ... }
  saveSnapshot(
    module?: string | undefined,
    test: string,
    snapName: string,
    serializedSnap: string) { ... }
})

Now in your tests, there's an extra method you can invoke on the assert object

QUnit.module('my test module');

QUnit.test('my first test', assert => {
  // Snapshot an object
  assert.snapshot({
    foo: 'bar',
    data: {
      key: 'value'
    }
  });
  // Snapshot a DOM element
  const elem = document.querySelector('.qunit-filter');
  assert.snapshot(elem);
});

If these snapshots don't yet exist, they'll be created (via your saveSnapshot hook). If existing snapshots are already found to exist (via your getSnapshot hook), assertions will be made to ensure the found value and expected value are deepEqual.

Example

As an example, the following configuration would use localstorage to store snapshot data. This file should be run before any tests.

import { install } from 'qunit-snapshot';
import { Snapshot } from 'qunit-snapshot';

function snapKey(
  moduleName: string,
  testName: string,
  snapName: string
): string {
  return ['snap', moduleName || '', testName, snapName]
    .map(k => k.replace(/[^A-Za-z0-9\-\_]+/, ''))
    .join('-');
}

install(QUnit, {
  getSnapshot(
    moduleName: string,
    testName: string,
    snapName: string
  ): Snapshot | undefined {
    // Create a key for localstorage like `snap-mymodule-mytest-1`
    const key = snapKey(moduleName, testName, snapName);
    // Attempt to retrieve an existing snapshot from localStorage
    const data = localStorage.getItem(key);
    if (!data) return; // If nothing is found, we return undefined
    // Try to regard the snapshot as a JSON value,
    let jData: any;
    try {
      jData = JSON.parse(data);
      return jData; // JSON parse worked, return the value
    } catch {
      // If parsing fails, but the raw value is truthy
      if (data) {
        return data; // return it directly
      }
      return; // Raw data was falsy. This is unreachable code anyway
    }
  },
  saveSnapshot(
    moduleName: string,
    testName: string,
    snapName: string,
    serializedSnap: string
  ): boolean {
    // Create a key for localstorage like `snap-mymodule-mytest-1`
    const key = snapKey(moduleName, testName, snapName);
    // Place the value in localStorage
    localStorage.setItem(key, serializedSnap);
    return true; // indicate success
  }
});

(c) 2018 LinkedIn