Registry / testing / it

it

JSON →
library1.0.0jsnpmunverified

"It" is a lightweight, behavior-driven development (BDD) style testing framework designed for both Node.js and browser environments, last known at version 1.1.1. It supports various asynchronous test patterns, including Promises and the traditional Mocha-style `done(err)` callback, and explicitly avoids polluting the global namespace. Key features include cross-environment compatibility, AMD support for browsers, multiple reporters (such as TAP for CI systems), and proper exit codes. Unlike some frameworks, `it` requires explicit CommonJS import and passes its context (`it`) into `describe` and `test` callbacks, promoting isolated test suites. Its development appears to be largely inactive, with the last stable release dating back significantly, making it less suitable for modern JavaScript projects requiring native ESM support or contemporary testing features.

testing
npm install it
github ↗package ↗
INSTALL
IMPORT
SIG · IT
I
it
testingjavascriptv1.0.0
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.

it
✓ const it = require('it');
✗ import { it } from 'it';
The primary testing function/object is exported via CommonJS. Direct ESM `import` statements will likely fail without a transpiler or wrapper.
it.describe
✓ const it = require('it'); it.describe('suite name', function(it) { /* ... */ });
✗ describe('suite name', function() { /* ... */ });
Unlike some frameworks, `it.describe` is a method of the imported `it` object, and the `it` context itself is passed into the callback, not a global.
it.should
✓ const it = require('it'); it.describe('suite', function(it) { it.should('do something', function() { /* ... */ }); });
✗ should('do something', function() { /* ... */ });
`it.should` is a convenience method for defining individual tests, acting as an alias for `it('should do something', ...)`.

Demonstrates defining a simple JavaScript class and writing hierarchical tests using `it.describe` and `it.should` with Node.js's built-in `assert` module.

var Person = function (name, age) { this.name = name; this.age = age; this.getOlder = function (years) { if (years > 0) { this.age = this.age + years; } }; }; var it = require("it"), assert = require("assert"); // Node.js built-in assert module it.describe("Person Object Tests", function (it) { it.should("correctly set name", function () { var person = new Person("Alice", 30); assert.strictEqual(person.name, "Alice"); }); it.should("correctly set age", function () { var person = new Person("Bob", 25); assert.strictEqual(person.age, 25); }); it.describe("#getOlder method", function (it) { it.should("increase age by positive numbers", function () { var person = new Person("Charlie", 40); person.getOlder(5); assert.strictEqual(person.age, 45); }); it.should("not modify age for negative numbers", function () { var person = new Person("David", 20); person.getOlder(-3); assert.strictEqual(person.age, 20); }); }); }); // To run this, save as a .js file and execute with Node.js: `node your-test-file.js`. // Alternatively, if `it` CLI is installed globally: `it your-test-file.js`.
it --version
Debug
Known issues
breakingThe `it` framework primarily uses CommonJS modules (`require`) and does not natively support ECMAScript Modules (ESM) `import` syntax. Attempting to use `import` directly in modern Node.js environments configured for ESM will result in errors.
fix
Ensure your project uses CommonJS, or transpile your code if you must use ESM syntax. Use `const it = require('it');` to import the module.
affects: >=1.0.0
gotchaThe `assert` module examples in the original `it` documentation (e.g., `assert.isFunction`) may imply a custom `assert` library or an older Node.js environment. Node.js's built-in `assert` module (especially in modern versions) primarily offers methods like `assert.strictEqual`, `assert.ok`, etc., and does not include `isFunction` directly. Using `assert.isFunction` with Node's built-in `assert` will result in a `TypeError`.
fix
Use standard Node.js `assert` methods (e.g., `assert.strictEqual`, `assert.ok`, `assert.throws`). If `assert.isFunction` is desired, you may need to install a separate assertion library (e.g., Chai's `assert` interface) and import it explicitly.
affects: >=1.0.0
gotchaThe `it` object is explicitly passed as an argument to `it.describe` and individual `it.should` (or `it()`) callbacks. This means `it` is not a global variable available throughout your test file. If you omit the parameter in a nested describe or test, `it` will be `undefined` within that scope.
fix
Always include `it` as a parameter in your `describe` and `should` callback functions (e.g., `it.describe('suite', function(it) { ... })`) to ensure the testing context is available.
affects: >=1.0.0
deprecatedThis package appears to be abandoned or in long-term maintenance, with no significant updates in recent years. Its reliance on older Node.js versions (>=0.10.1) and older CI systems (Travis CI, Testling CI) suggests it may not be compatible with newer JavaScript features, Node.js APIs, or modern testing practices.
fix
Consider migrating to a more actively maintained testing framework like Jest, Mocha, or Vitest for modern JavaScript development.
affects: >=1.0.0
Errors
Common errors & fixes
ReferenceError: it is not defined
Attempting to use `it.describe` or `it.should` without correctly importing the `it` module first, or trying to use `it` globally in a scope where it hasn't been passed as an argument.
fix
Ensure you have `const it = require('it');` at the top of your test file, and that the `it` object is passed into your `describe` and test callbacks: `it.describe('My Suite', function(it) { ... })`.
TypeError: assert.isFunction is not a function
Using `assert.isFunction` or similar non-standard `assert` methods with Node.js's built-in `assert` module, which does not provide these methods.
fix
Replace calls to `assert.isFunction` with standard Node.js `assert` methods like `assert.strictEqual(typeof myVar, 'function')` or consider using an alternative assertion library like Chai (`assert`, `expect`, or `should` styles) which offers a broader range of assertions.
SyntaxError: Cannot use import statement outside a module
Trying to use `import { it } from 'it';` in a Node.js environment that is not configured for ES Modules, or when the `it` package itself is a CommonJS module.
fix
Use the CommonJS `require` syntax: `const it = require('it');`. If you are in an ES Module context, you may need to use `import it from 'it'` if it provides a default export, or consider a build step that transforms CommonJS to ESM.
Upgrade
Version history
1.0.0latest on npm
Audit
Dependencies

No dependency data recorded yet.

Agent activity
4 hits · last 30 days
node
4
Resources
githubhttps://github.com/doug-martin/it ↗
packagehttps://www.npmjs.com/package/it ↗
it — npm install it · libregistry