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

@atakama/qtest

v1.6.5

Published

quick and simple test runner for nodejs (alternative to jest)

Downloads

50

Readme

Build Status codecov

qtest

Simple test runner for nodejs.

Install:

npm install @atakama/qtest

Use:

test = require('@atakama/qtest')
assert = require('assert')

test("test name", async (ctx)=>{
    ctx.log("some log")

    assert.equal(ctx.someFixture, 444)

    // parameterized test
    assert.equal(ctx.param, true)
}, {param: [true, false]})

test.beforeAll = async (ctx) => {
    ctx.someFixture = 444
}

test.run()

Coverage:

npm install nyc
node_modules/.bin/nyc node test.js

Other features:

  • cli options
    • -t <test-name> : pick a test to run
    • -l : disable parallelism
    • -s : disable log cap
  • before/after/beforeAll/afterAll
    • does what you expect
  • fixtures
    • beforeAll/before/after/afterAll take objects... stuff your fixtures in there
  • test.skip(...)
  • t = test.scope("name")
    • creates a new, scoped test collection
    • will get run if the parent is run
  • yarn add --dev sinon for asseritions, mocks, and spies
    • see sinonjs.org for more details
    • test.assert will include augmented assertions (assert.calledOnce, et al)
    • test.spy, test.stub, ... aliased to sinon equivalents
    • some jesty aliases:
      • test.fn == sinon.fake
      • test.replaceFn = sinon.replace
      • test.argsMatch = sinon.match
  • unawaited promise handling
    • async calls that linger are considered failures
    • unawaited promise rejections are failures

Babel:

Example package.json using babel and coverage:

  "scripts": {
    "test": "babel-node --ignore nothing test.js",
    "coverage": "nyc npm run test"
  },
  "nyc": {
    "require": [
      "@babel/register"
    ],
    "reporter": [
      "lcov",
      "text"
    ]

Webstorm or VSCode interactive debugger

On Windows, you cannot set the interpreter to babel-node, because it's a cmd file and that causes most debuggers to get confused. This config works on all debuggers:

  • Click Run/Edit Configurations..
  • Set NodeParameters: node_modules/@babel/node/bin/babel-node.js --ignore nothing --
  • Optionally set Application parameters: -t <your test name

Changelog