test-machinepack

library3.0.1jsnpmunverified

test-machinepack provides a raw command-line test runner specifically designed for `node-machine` 'machinepacks'. Its current stable version is 3.0.1, though the last known development activity dates back to 2017, suggesting it is in maintenance mode rather than active development. While it includes a basic, generic test driver, the documentation explicitly recommends against using it for production testing, instead pointing to more robust, community-maintained drivers like `test-machinepack-mocha`. The primary function of this package is to expose a consistent interface for running tests defined in JSON or JSON5 format within a machinepack's `tests` directory, thereby enabling custom test drivers to integrate seamlessly with the `node-machine` ecosystem.

testing devops

npm install test-machinepack

github ↗package ↗

INSTALL

IMPORT

SIG · TEST-MACHINEPACK

test-machinepack

testingjavascriptv3.0.1

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

testmachinepack CLI

✓ testmachinepack

✗ node testmachinepack

The primary way to use this package is via its globally installed CLI command. Installation via `npm install -g` is typically required.

runTests

✓ const runTests = require('test-machinepack');

✗ import { runTests } from 'test-machinepack';

Programmatic usage is primarily for building custom test drivers. The package exports a single function as its default (CommonJS) export. ESM named imports will not work.

runTests (ESM)

✓ import runTests from 'test-machinepack';

✗ import * as testMachinepack from 'test-machinepack';

While primarily a CommonJS package from 2017, modern bundlers can often handle importing the default CommonJS export as an ESM default import.

Demonstrates global installation and basic CLI usage of `test-machinepack` to run tests defined in a JSON5 file within a simulated machinepack structure.

npm install -g test-machinepack mkdir my-awesome-machinepack cd my-awesome-machinepack # Assuming you have `machinepack` installed globally to use `pm scrub` # npm install -g machinepack pm scrub mkdir tests cat > tests/example-machine.json5 <<EOF { "machine": "example-machine", "expectations": [ { "using": { "input1": "hello" }, "outcome": "success" }, { "using": { "input1": "" }, "outcome": "error", "todo": true } ] } EOF # Run tests using the built-in (basic) driver testmachinepack

Debug

Known issues

gotchaThe built-in test driver included with `test-machinepack` is explicitly labeled as 'pretty basic' and not recommended for serious use. Users are encouraged to utilize external drivers, such as `test-machinepack-mocha`, for more robust and feature-rich testing.

fix

Migrate to a recommended external test driver (e.g., `test-machinepack-mocha`) for comprehensive testing needs. This module should primarily be used for its runner interface for custom drivers.

affects: >=1.0.0

deprecatedThe package appears to be unmaintained since 2017 based on its GitHub activity and copyright dates. While functional, it may not receive updates for new Node.js versions or security fixes, potentially leading to compatibility issues.

fix

Evaluate the stability and compatibility with your current Node.js environment. For new projects, consider alternatives or be prepared to fork and maintain the package yourself if extensive `node-machine` testing is required.

affects: >=1.0.0

gotchaTest definitions are written in JSON or JSON5 format, which differs significantly from traditional JavaScript/TypeScript test files. This can be a steep learning curve for developers unfamiliar with the `node-machine` convention.

fix

Familiarize yourself with the `node-machine` test specification and the JSON/JSON5 structure. Refer to the examples provided in `machinepack-npm`'s test directory for practical usage patterns.

affects: >=1.0.0

Errors

Common errors & fixes

command not found: testmachinepack

The `testmachinepack` command-line utility was not installed globally or is not in your system's PATH.

fix

Install the package globally using `npm install -g test-machinepack`.

Error: Failed to parse test file: [filepath].json5 (SyntaxError: Unexpected token ...)

The JSON or JSON5 test file contains syntax errors, making it unparseable by the runner.

fix

Carefully review the specified test file for malformed JSON or JSON5 syntax. Tools like `jsonlint` or online JSON validators can help identify issues.

Error: Could not find 'machine' with identity 'some-machine' in the current machinepack.

The `machine` property in your test file refers to a machine identity that does not exist or is not exposed by your machinepack.

fix

Ensure the `machine` property in your JSON/JSON5 test file exactly matches the identity of an existing machine within your machinepack. Verify the machine's file name and export.

Upgrade

Version history

3.0.1latest on npm

Audit

Dependencies

machinepackrequiredRequired for generating skeleton test files ('pm scrub') and for the core functionality of running tests against machine definitions.

Agent activity

5 hits · last 30 days

node

OpenAI (training)

Resources

githubhttps://github.com/mikermcneil/test-machinepack ↗

packagehttps://www.npmjs.com/package/test-machinepack ↗