@atakama/qtest

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