Test runner | Node.js v26.5.0 Documentation

Skip to content
Table of contents

- Test runner
  - Subtests
  - Rerunning failed tests
  - `describe()` and `it()` aliases
  - Skipping tests
  - TODO tests
  - Expecting tests to fail
  - `only` tests
  - Filtering tests by name
  - Test tags
    - Authoring tagged tests
    - Filtering by tag
    - Reading tags from inside a test
    - Errors
  - Extraneous asynchronous activity
  - Watch mode
  - Global setup and teardown
  - Running tests from the command line
    - Randomizing tests execution order
    - Test runner execution model
      - Child process option inheritance
  - Collecting code coverage
    - Coverage reporters
  - Mocking
    - Timers
    - Dates
  - Snapshot testing
  - Test reporters
    - Custom reporters
    - Multiple reporters
  - `run([options])`
  - `suite([name][, options][, fn])`
  - `suite.skip([name][, options][, fn])`
  - `suite.todo([name][, options][, fn])`
  - `suite.only([name][, options][, fn])`
  - `test([name][, options][, fn])`
  - `test.skip([name][, options][, fn])`
  - `test.todo([name][, options][, fn])`
  - `test.only([name][, options][, fn])`
  - `describe([name][, options][, fn])`
  - `describe.skip([name][, options][, fn])`
  - `describe.todo([name][, options][, fn])`
  - `describe.only([name][, options][, fn])`
  - `it([name][, options][, fn])`
  - `it.skip([name][, options][, fn])`
  - `it.todo([name][, options][, fn])`
  - `it.only([name][, options][, fn])`
  - `before([fn][, options])`
  - `after([fn][, options])`
  - `beforeEach([fn][, options])`
  - `afterEach([fn][, options])`
  - `assert`
    - `assert.register(name, fn)`
  - `snapshot`
    - `snapshot.setDefaultSnapshotSerializers(serializers)`
    - `snapshot.setResolveSnapshotPath(fn)`
  - Class: `MockFunctionContext`
    - `ctx.calls`
    - `ctx.callCount()`
    - `ctx.mockImplementation(implementation)`
    - `ctx.mockImplementationOnce(implementation[, onCall])`
    - `ctx.resetCalls()`
    - `ctx.restore()`
  - Class: `MockModuleContext`
    - `ctx.restore()`
  - Class: `MockPropertyContext`
    - `ctx.accesses`
    - `ctx.accessCount()`
    - `ctx.mockImplementation(value)`
    - `ctx.mockImplementationOnce(value[, onAccess])`
      - Caveat
    - `ctx.resetAccesses()`
    - `ctx.restore()`
  - Class: `MockTracker`
    - `mock.fn([original[, implementation]][, options])`
    - `mock.getter(object, methodName[, implementation][, options])`
    - `mock.method(object, methodName[, implementation][, options])`
    - `mock.module(specifier[, options])`
    - `mock.property(object, propertyName[, value])`
    - `mock.reset()`
    - `mock.restoreAll()`
    - `mock.setter(object, methodName[, implementation][, options])`
  - Class: `MockTimers`
    - `timers.enable([enableOptions])`
    - `timers.reset()`
    - `timers[Symbol.dispose]()`
    - `timers.tick([milliseconds])`
      - Using clear functions
      - Working with Node.js timers modules
    - `timers.runAll()`
    - `timers.setTime(milliseconds)`
      - Dates and Timers working together
  - Class: `TestsStream`
    - Event: `'test:coverage'`
    - Event: `'test:complete'`
    - Event: `'test:dequeue'`
    - Event: `'test:diagnostic'`
    - Event: `'test:enqueue'`
    - Event: `'test:fail'`
    - Event: `'test:interrupted'`
    - Event: `'test:pass'`
    - Event: `'test:plan'`
    - Event: `'test:start'`
    - Event: `'test:stderr'`
    - Event: `'test:stdout'`
    - Event: `'test:summary'`
    - Event: `'test:watch:drained'`
    - Event: `'test:watch:restarted'`
  - `getTestContext()`
  - Test instrumentation and OpenTelemetry
    - Tracing events
      - Channel: `'tracing:node.test:start'`
      - Channel: `'tracing:node.test:end'`
      - Channel: `'tracing:node.test:error'`
    - Context propagation with `bindStore()`
  - Class: `TestContext`
    - `context.before([fn][, options])`
    - `context.beforeEach([fn][, options])`
    - `context.after([fn][, options])`
    - `context.afterEach([fn][, options])`
    - `context.assert`
      - `context.assert.fileSnapshot(value, path[, options])`
      - `context.assert.snapshot(value[, options])`
    - `context.diagnostic(message)`
    - `context.filePath`
    - `context.fullName`
    - `context.name`
    - `context.passed`
    - `context.error`
    - `context.attempt`
    - `context.tags`
    - `context.workerId`
    - `context.plan(count[,options])`
    - `context.runOnly(shouldRunOnlyTests)`
    - `context.signal`
    - `context.skip([message])`
    - `context.todo([message])`
    - `context.test([name][, options][, fn])`
    - `context.waitFor(condition[, options])`
  - Class: `SuiteContext`
    - `context.filePath`
    - `context.fullName`
    - `context.name`
    - `context.signal`
    - `context.passed`
    - `context.attempt`
    - `context.diagnostic(message)`

## Test runner#

Source Code: lib/test.js Added in: v18.0.0, v16.17.0
History

Version | Changes
--- | ---
v20.0.0 | The test runner is now stable.

Stability: 2 - Stable

The `node:test` module facilitates the creation of JavaScript tests. To access it:

    import test from 'node:test';
    const test = require('node:test');
    javascript

This module is only available under the `node:` scheme.

Tests created via the `test` module consist of a single function that is processed in one of three ways:

1. A synchronous function that is considered failing if it throws an exception, and is considered passing otherwise.
2. A function that returns a `Promise` that is considered failing if the `Promise` rejects, and is considered passing if the `Promise` fulfills.
3. A function that receives a callback function. If the callback receives any truthy value as its first argument, the test is considered failing. If a falsy value is passed as the first argument to the callback, the test is considered passing. If the test function receives a callback function and also returns a `Promise`, the test will fail.

The following example illustrates how tests are written using the `test` module.

    test('synchronous passing test', (t) => {
      // This test passes because it does not throw an exception.
      assert.strictEqual(1, 1);
    });

    test('synchronous failing test', (t) => {
      // This test fails because it throws an exception.
      assert.strictEqual(1, 2);
    });

    test('asynchronous passing test', async (t) => {
      // This test passes because the Promise returned by the async
      // function is settled and not rejected.
      assert.strictEqual(1, 1);
    });

    test('asynchronous failing test', async (t) => {
      // This test fails because the Promise returned by the async
      // function is rejected.
      assert.strictEqual(1, 2);
    });

    test('failing test using Promises', (t) => {
      // Promises can be used directly as well.
      return new Promise((resolve, reject) => {
        setImmediate(() => {
          reject(new Error('this will cause the test to fail'));
        });
      });
    });

    test('callback passing test', (t, done) => {
      // done() is the callback function. When the setImmediate() runs, it invokes
      // done() with no arguments.
      setImmediate(done);
    });

    test('callback failing test', (t, done) => {
      // When the setImmediate() runs, done() is invoked with an Error object and
      // the test fails.
      setImmediate(() => {
        done(new Error('callback failure'));
      });
    });
    js

If any tests fail, the process exit code is set to `1`.

### Subtests#

The test context's `test()` method allows subtests to be created. It allows you to structure your tests in a hierarchical manner, where you can create nested tests within a larger test. This method behaves identically to the top level `test()` function. The following example demonstrates the creation of a top level test with two subtests.

    test('top level test', async (t) => {
      await t.test('subtest 1', (t) => {
        assert.strictEqual(1, 1);
      });

      await t.test('subtest 2', (t) => {
        assert.strictEqual(2, 2);
      });
    });
    js

> Note: `beforeEach` and `afterEach` hooks are triggered between each subtest execution.

In this example, `await` is used to ensure that both subtests have completed. This is necessary because tests do not wait for their subtests to complete, unlike tests created within suites. Any subtests that are still outstanding when their parent finishes are cancelled and treated as failures. Any subtest failures cause the parent test to fail.

### Rerunning failed tests#

The test runner supports persisting the state of the run to a file, allowing the test runner to rerun failed tests without having to re-run the entire test suite. Use the `--test-rerun-failures` command-line option to specify a file path where the state of the run is stored. if the state file does not exist, the test runner will create it. the state file is a JSON file that contains an array of run attempts. Each run attempt is an object mapping successful tests to the attempt they have passed in. The key identifying a test in this map is the test file path, with the line and column where the test is defined. in a case where a test defined in a specific location is run multiple times, for example within a function or a loop, a counter will be appended to the key, to disambiguate the test runs. note changing the order of test execution or the location of a test can lead the test runner to consider tests as passed on a previous attempt, meaning `--test-rerun-failures` should be used when tests run in a deterministic order.

example of a state file:

    [
      {
        "test.js:10:5": { "passed_on_attempt": 0, "name": "test 1" }
      },
      {
        "test.js:10:5": { "passed_on_attempt": 0, "name": "test 1" },
        "test.js:20:5": { "passed_on_attempt": 1, "name": "test 2" }
      }
    ]
    json

in this example, there are two run attempts, with two tests defined in `test.js`, the first test succeeded on the first attempt, and the second test succeeded on the second attempt.

When the `--test-rerun-failures` option is used, the test runner will only run tests that have not yet passed.

    node --test-rerun-failures /path/to/state/file
    bash

### `describe()` and `it()` aliases#

Suites and tests can also be written using the `describe()` and `it()` functions. `describe()` is an alias for `suite()`, and `it()` is an alias for `test()`.

    describe('A thing', () => {
      it('should work', () => {
        assert.strictEqual(1, 1);
      });

      it('should be ok', () => {
        assert.strictEqual(2, 2);
      });

      describe('a nested thing', () => {
        it('should work', () => {
          assert.strictEqual(3, 3);
        });
      });
    });
    js

`describe()` and `it()` are imported from the `node:test` module.

    import { describe, it } from 'node:test';
    const { describe, it } = require('node:test');
    javascript

### Skipping tests#

Individual tests can be skipped by passing the `skip` option to the test, or by calling the test context's `skip()` method as shown in the following example.

    // The skip option is used, but no message is provided.
    test('skip option', { skip: true }, (t) => {
      // This code is never executed.
    });

    // The skip option is used, and a message is provided.
    test('skip option with message', { skip: 'this is skipped' }, (t) => {
      // This code is never executed.
    });

    test('skip() method', (t) => {
      // Make sure to return here as well if the test contains additional logic.
      t.skip();
    });

    test('skip() method with message', (t) => {
      // Make sure to return here as well if the test contains additional logic.
      t.skip('this is skipped');
    });
    js

### TODO tests#

Individual tests can be marked as flaky or incomplete by passing the `todo` option to the test, or by calling the test context's `todo()` method, as shown in the following example. These tests represent a pending implementation or bug that needs to be fixed. TODO tests are executed, but are not treated as test failures, and therefore do not affect the process exit code. If a test is marked as both TODO and skipped, the TODO option is ignored.

    // The todo option is used, but no message is provided.
    test('todo option', { todo: true }, (t) => {
      // This code is executed, but not treated as a failure.
      throw new Error('this does not fail the test');
    });

    // The todo option is used, and a message is provided.
    test('todo option with message', { todo: 'this is a todo test' }, (t) => {
      // This code is executed.
    });

    test('todo() method', (t) => {
      t.todo();
    });

    test('todo() method with message', (t) => {
      t.todo('this is a todo test and is not treated as a failure');
      throw new Error('this does not fail the test');
    });
    js

### Expecting tests to fail#

Added in: v25.5.0, v24.14.0

This flips the pass/fail reporting for a specific test or suite: a flagged test case must throw in order to pass, and a flagged test case that does not throw fails.

In each of the following, `doTheThing()` fails to return `true`, but since the tests are flagged `expectFailure`, they pass.

    it.expectFailure('should do the thing', () => {
      assert.strictEqual(doTheThing(), true);
    });

    it('should do the thing', { expectFailure: true }, () => {
      assert.strictEqual(doTheThing(), true);
    });

    it('should do the thing', { expectFailure: 'feature not implemented' }, () => {
      assert.strictEqual(doTheThing(), true);
    });
    js

If the value of `expectFailure` is a `<RegExp>` | `<Function>` | `<Object>` | `<Error>` the tests will pass only if they throw a matching value. See `assert.throws` for how each value type is handled.

Each of the following tests fails despite being flagged `expectFailure` because the failure does not match the specific expected failure.

    it('fails because regex does not match', {
      expectFailure: /expected message/,
    }, () => {
      throw new Error('different message');
    });

    it('fails because object matcher does not match', {
      expectFailure: { code: 'ERR_EXPECTED' },
    }, () => {
      const err = new Error('boom');
      err.code = 'ERR_ACTUAL';
      throw err;
    });
    js

To supply both a reason and specific error for `expectFailure`, use `{ label, match }`.

    it('should fail with specific error and reason', {
      expectFailure: {
        label: 'reason for failure',
        match: /error message/,
      },
    }, () => {
      assert.strictEqual(doTheThing(), true);
    });
    js

`skip` and/or `todo` are mutually exclusive to `expectFailure`, and `skip` or `todo` will "win" when both are applied (`skip` wins against both, and `todo` wins against `expectFailure`).

These tests will be skipped (and not run):

    it.expectFailure('should do the thing', { skip: true }, () => {
      assert.strictEqual(doTheThing(), true);
    });

    it.skip('should do the thing', { expectFailure: true }, () => {
      assert.strictEqual(doTheThing(), true);
    });
    js

These tests will be marked "todo" (silencing errors):

    it.expectFailure('should do the thing', { todo: true }, () => {
      assert.strictEqual(doTheThing(), true);
    });

    it.todo('should do the thing', { expectFailure: true }, () => {
      assert.strictEqual(doTheThing(), true);
    });
    js

### `only` tests#

If Node.js is started with the `--test-only` command-line option, or test isolation is disabled, it is possible to skip all tests except for a selected subset by passing the `only` option to the tests that should run. When a test with the `only` option is set, all subtests are also run. If a suite has the `only` option set, all tests within the suite are run, unless it has descendants with the `only` option set, in which case only those tests are run.

When using subtests within a `test()`/`it()`, it is required to mark all ancestor tests with the `only` option to run only a selected subset of tests.

The test context's `runOnly()` method can be used to implement the same behavior at the subtest level. Tests that are not executed are omitted from the test runner output.

    // Assume Node.js is run with the --test-only command-line option.
    // The suite's 'only' option is set, so these tests are run.
    test('this test is run', { only: true }, async (t) => {
      // Within this test, all subtests are run by default.
      await t.test('running subtest');

      // The test context can be updated to run subtests with the 'only' option.
      t.runOnly(true);
      await t.test('this subtest is now skipped');
      await t.test('this subtest is run', { only: true });

      // Switch the context back to execute all tests.
      t.runOnly(false);
      await t.test('this subtest is now run');

      // Explicitly do not run these tests.
      await t.test('skipped subtest 3', { only: false });
      await t.test('skipped subtest 4', { skip: true });
    });

    // The 'only' option is not set, so this test is skipped.
    test('this test is not run', () => {
      // This code is not run.
      throw new Error('fail');
    });

    describe('a suite', () => {
      // The 'only' option is set, so this test is run.
      it('this test is run', { only: true }, () => {
        // This code is run.
      });

      it('this test is not run', () => {
        // This code is not run.
        throw new Error('fail');
      });
    });

    describe.only('a suite', () => {
      // The 'only' option is set, so this test is run.
      it('this test is run', () => {
        // This code is run.
      });

      it('this test is run', () => {
        // This code is run.
      });
    });
    js

### Filtering tests by name#

The `--test-name-pattern` command-line option can be used to only run tests whose name matches the provided pattern, and the `--test-skip-pattern` option can be used to skip tests whose name matches the provided pattern. Test name patterns are interpreted as JavaScript regular expressions. The `--test-name-pattern` and `--test-skip-pattern` options can be specified multiple times in order to run nested tests. For each test that is executed, any corresponding test hooks, such as `beforeEach()`, are also run. Tests that are not executed are omitted from the test runner output.

Given the following test file, starting Node.js with the `--test-name-pattern="test [1-3]"` option would cause the test runner to execute `test 1`, `test 2`, and `test 3`. If `test 1` did not match the test name pattern, then its subtests would not execute, despite matching the pattern. The same set of tests could also be executed by passing `--test-name-pattern` multiple times (e.g. `--test-name-pattern="test 1"`, `--test-name-pattern="test 2"`, etc.).

    test('test 1', async (t) => {
      await t.test('test 2');
      await t.test('test 3');
    });

    test('Test 4', async (t) => {
      await t.test('Test 5');
      await t.test('test 6');
    });
    js

Test name patterns can also be specified using regular expression literals. This allows regular expression flags to be used. In the previous example, starting Node.js with `--test-name-pattern="/test [4-5]/i"` (or `--test-skip-pattern="/test [4-5]/i"`) would match `Test 4` and `Test 5` because the pattern is case-insensitive.

To match a single test with a pattern, you can prefix it with all its ancestor test names separated by space, to ensure it is unique. For example, given the following test file:

    describe('test 1', (t) => {
      it('some test');
    });

    describe('test 2', (t) => {
      it('some test');
    });
    js

Starting Node.js with `--test-name-pattern="test 1 some test"` would match only `some test` in `test 1`.

Test name patterns do not change the set of files that the test runner executes.

If both `--test-name-pattern` and `--test-skip-pattern` are supplied, tests must satisfy both requirements in order to be executed.

### Test tags#

Added in: v26.2.0

Stability: 1.0 - Early development

Tags annotate tests and suites with arbitrary string labels. The `--experimental-test-tag-filter` CLI flag (or the `testTagFilters` option on `run()`) selects tests whose tag set contains every provided filter value.

Tags are an alternative to encoding metadata into test names. They are useful for cross-cutting axes such as subsystem, speed bucket, flakiness, or environment, where a name pattern would be brittle.

#### Authoring tagged tests#

Pass a `tags` array on any of `test()`, `it()`, `suite()`, or `describe()`. Tags inherit from a suite to its child tests by union—a test inside a suite tagged `['db']` that declares its own `tags: ['integration']` effectively has both tags.

    import { describe, it } from 'node:test';

    describe('database', { tags: ['db'] }, () => {
      it('reads a row');                                            // tags: ['db']
      it('writes a row', { tags: ['integration'] });                // tags: ['db', 'integration']
      it('reconnects after disconnect', { tags: ['flaky'] });       // tags: ['db', 'flaky']
    });
    const { describe, it } = require('node:test');

    describe('database', { tags: ['db'] }, () => {
      it('reads a row');                                            // tags: ['db']
      it('writes a row', { tags: ['integration'] });                // tags: ['db', 'integration']
      it('reconnects after disconnect', { tags: ['flaky'] });       // tags: ['db', 'flaky']
    });
    javascript

Tag values must be non-empty strings. Tags are matched case-insensitively; the canonical form is lowercase. Duplicates within a single `tags` array are collapsed on the lowercased form, preserving the first-seen declaration order.

Hooks (`before`, `after`, `beforeEach`, `afterEach`) do not declare their own tags. They run as part of their owning suite, which carries the suite's tags.

#### Filtering by tag#

Each `--experimental-test-tag-filter` value is a literal tag name. A test runs only when its tag set contains that name. The flag may be specified more than once; tests must match every filter to run. The same applies to the `testTagFilters` array on `run()`. Filters are case-insensitive and AND'd with `--test-name-pattern`, `--test-skip-pattern`, and `.only` filtering.

Untagged tests are excluded under any non-empty filter, since the filter requires the tag to be present.

#### Reading tags from inside a test#

The `TestContext` object exposes the test's tags as a frozen array through `context.tags`, so tests can branch on their own metadata.

#### Errors#

A tag value that violates the validation rules above throws `ERR_INVALID_ARG_VALUE` at the registration site, before any test runs. A non-array `tags` value throws `ERR_INVALID_ARG_TYPE`.

### Extraneous asynchronous activity#

Once a test function finishes executing, the results are reported as quickly as possible while maintaining the order of the tests. However, it is possible for the test function to generate asynchronous activity that outlives the test itself. The test runner handles this type of activity, but does not delay the reporting of test results in order to accommodate it.

In the following example, a test completes with two `setImmediate()` operations still outstanding. The first `setImmediate()` attempts to create a new subtest. Because the parent test has already finished and output its results, the new subtest is immediately marked as failed, and reported later to the `<TestsStream>`.

The second `setImmediate()` creates an `uncaughtException` event. `uncaughtException` and `unhandledRejection` events originating from a completed test are marked as failed by the `test` module and reported as diagnostic warnings at the top level by the `<TestsStream>`.

    test('a test that creates asynchronous activity', (t) => {
      setImmediate(() => {
        t.test('subtest that is created too late', (t) => {
          throw new Error('error1');
        });
      });

      setImmediate(() => {
        throw new Error('error2');
      });

      // The test finishes after this line.
    });
    js

### Watch mode#

Added in: v19.2.0, v18.13.0

Stability: 1 - Experimental

The Node.js test runner supports running in watch mode by passing the `--watch` flag:

    node --test --watch
    bash

In watch mode, the test runner will watch for changes to test files and their dependencies. When a change is detected, the test runner will rerun the tests affected by the change. The test runner will continue to run until the process is terminated.

### Global setup and teardown#

Added in: v24.0.0

Stability: 1.0 - Early development

The test runner supports specifying a module that will be evaluated before all tests are executed and can be used to setup global state or fixtures for tests. This is useful for preparing resources or setting up shared state that is required by multiple tests.

This module can export any of the following:

- A `globalSetup` function which runs once before all tests start
- A `globalTeardown` function which runs once after all tests complete

The module is specified using the `--test-global-setup` flag when running tests from the command line.

    // setup-module.js
    async function globalSetup() {
      // Setup shared resources, state, or environment
      console.log('Global setup executed');
      // Run servers, create files, prepare databases, etc.
    }

    async function globalTeardown() {
      // Clean up resources, state, or environment
      console.log('Global teardown executed');
      // Close servers, remove files, disconnect from databases, etc.
    }

    module.exports = { globalSetup, globalTeardown };
    // setup-module.mjs
    export async function globalSetup() {
      // Setup shared resources, state, or environment
      console.log('Global setup executed');
      // Run servers, create files, prepare databases, etc.
    }

    export async function globalTeardown() {
      // Clean up resources, state, or environment
      console.log('Global teardown executed');
      // Close servers, remove files, disconnect from databases, etc.
    }
    javascript

If the global setup function throws an error, no tests will be run and the process will exit with a non-zero exit code. The global teardown function will not be called in this case.

### Running tests from the command line#

The Node.js test runner can be invoked from the command line by passing the `--test` flag:

    node --test
    bash

By default, Node.js will run all files matching these patterns:

- `**/*.test.{cjs,mjs,js}`
- `**/*-test.{cjs,mjs,js}`
- `**/*_test.{cjs,mjs,js}`
- `**/test-*.{cjs,mjs,js}`
- `**/test.{cjs,mjs,js}`
- `**/test/**/*.{cjs,mjs,js}`

Unless `--no-strip-types` is supplied, the following additional patterns are also matched:

- `**/*.test.{cts,mts,ts}`
- `**/*-test.{cts,mts,ts}`
- `**/*_test.{cts,mts,ts}`
- `**/test-*.{cts,mts,ts}`
- `**/test.{cts,mts,ts}`
- `**/test/**/*.{cts,mts,ts}`

Alternatively, one or more glob patterns can be provided as the final argument(s) to the Node.js command, as shown below. Glob patterns follow the behavior of `glob(7)`. The glob patterns should be enclosed in double quotes on the command line to prevent shell expansion, which can reduce portability across systems.

    node --test "**/*.test.js" "**/*.spec.js"
    bash

#### Randomizing tests execution order#

Added in: v26.1.0

Stability: 1.0 - Early development

The test runner can randomize execution order to help detect order-dependent tests. When enabled, the runner randomizes both discovered test files and queued tests within each file. Use `--test-randomize` to enable this mode.

    node --test --test-randomize
    bash

When randomization is enabled, the test runner prints the seed used for the run as a diagnostic message:

    Randomized test order seed: 12345
    text

Use `--test-random-seed=<number>` to replay the same randomized order deterministically. Supplying `--test-random-seed` also enables randomization, so `--test-randomize` is optional when a seed is provided:

    node --test --test-random-seed=12345
    bash

In most test files, randomization works automatically. One important exception is when subtests are awaited one by one. In that pattern, each subtest starts only after the previous one finishes, so the runner keeps declaration order instead of randomizing it.

Example: this runs sequentially and is not randomized.

    import test from 'node:test';

    test('math', async (t) => {
      for (const name of ['adds', 'subtracts', 'multiplies']) {
        // Sequentially awaiting each subtest preserves declaration order.
        await t.test(name, async () => {});
      }
    });
    const test = require('node:test');

    test('math', async (t) => {
      for (const name of ['adds', 'subtracts', 'multiplies']) {
        // Sequentially awaiting each subtest preserves declaration order.
        await t.test(name, async () => {});
      }
    });
    javascript

Using suite-style APIs such as `describe()`/`it()` or `suite()`/`test()` still allows randomization, because sibling tests are enqueued together.

Example: this remains eligible for randomization.

    import { describe, it } from 'node:test';

    describe('math', () => {
      it('adds', () => {});
      it('subtracts', () => {});
      it('multiplies', () => {});
    });
    const { describe, it } = require('node:test');

    describe('math', () => {
      it('adds', () => {});
      it('subtracts', () => {});
      it('multiplies', () => {});
    });
    javascript

`--test-randomize` and `--test-random-seed` are not supported with `--watch` mode.

Matching files are executed as test files. More information on the test file execution can be found in the test runner execution model section.

#### Test runner execution model#

When process-level test isolation is enabled, each matching test file is executed in a separate child process. The maximum number of child processes running at any time is controlled by the `--test-concurrency` flag. If the child process finishes with an exit code of 0, the test is considered passing. Otherwise, the test is considered to be a failure. Test files must be executable by Node.js, but are not required to use the `node:test` module internally.

Each test file is executed as if it was a regular script. That is, if the test file itself uses `node:test` to define tests, all of those tests will be executed within a single application thread, regardless of the value of the `concurrency` option of `test()`.

When process-level test isolation is disabled, each matching test file is imported into the test runner process. Once all test files have been loaded, the top level tests are executed with a concurrency of one. Because the test files are all run within the same context, it is possible for tests to interact with each other in ways that are not possible when isolation is enabled. For example, if a test relies on global state, it is possible for that state to be modified by a test originating from another file.

##### Child process option inheritance#

When running tests in process isolation mode (the default), spawned child processes inherit Node.js options from the parent process, including those specified in configuration files. However, certain flags are filtered out to enable proper test runner functionality:

- `--test` - Prevented to avoid recursive test execution
- `--experimental-test-coverage` - Managed by the test runner
- `--experimental-test-tag-filter` - Filter values are validated by the parent process and re-emitted to child processes
- `--watch` - Watch mode is handled at the parent level
- `--experimental-default-config-file` - Config file loading is handled by the parent
- `--test-reporter` - Reporting is managed by the parent process
- `--test-reporter-destination` - Output destinations are controlled by the parent
- `--experimental-config-file` - Config file paths are managed by the parent
- `--test-randomize` - Randomization is managed by the parent process and propagated to child processes
- `--test-random-seed` - Randomization seed is managed by the parent process and propagated to child processes

All other Node.js options from command line arguments, environment variables, and configuration files are inherited by the child processes.

### Collecting code coverage#

Stability: 1 - Experimental

When Node.js is started with the `--experimental-test-coverage` command-line flag, code coverage is collected and statistics are reported once all tests have completed. If the `NODE_V8_COVERAGE` environment variable is used to specify a code coverage directory, the generated V8 coverage files are written to that directory. Node.js core modules and files within `node_modules/` directories are, by default, not included in the coverage report. However, they can be explicitly included via the `--test-coverage-include` flag. By default all the matching test files are excluded from the coverage report. Exclusions can be overridden by using the `--test-coverage-exclude` flag. If coverage is enabled, the coverage report is sent to any test reporters via the `'test:coverage'` event.

Coverage can be disabled on a series of lines using the following comment syntax:

    /* node:coverage disable */
    if (anAlwaysFalseCondition) {
      // Code in this branch will never be executed, but the lines are ignored for
      // coverage purposes. All lines following the 'disable' comment are ignored
      // until a corresponding 'enable' comment is encountered.
      console.log('this is never executed');
    }
    /* node:coverage enable */
    js

Coverage can also be disabled for a specified number of lines. After the specified number of lines, coverage will be automatically reenabled. If the number of lines is not explicitly provided, a single line is ignored.

    /* node:coverage ignore next */
    if (anAlwaysFalseCondition) { console.log('this is never executed'); }

    /* node:coverage ignore next 3 */
    if (anAlwaysFalseCondition) {
      console.log('this is never executed');
    }
    js

#### Coverage reporters#

The tap and spec reporters will print a summary of the coverage statistics. There is also an lcov reporter that will generate an lcov file which can be used as an in depth coverage report.

    node --test --experimental-test-coverage --test-reporter=lcov --test-reporter-destination=lcov.info
    bash

- No test results are reported by this reporter.
- This reporter should ideally be used alongside another reporter.

### Mocking#

The `node:test` module supports mocking during testing via a top-level `mock` object. The following example creates a spy on a function that adds two numbers together. The spy is then used to assert that the function was called as expected.

    import assert from 'node:assert';
    import { mock, test } from 'node:test';

    test('spies on a function', () => {
      const sum = mock.fn((a, b) => {
        return a + b;
      });

      assert.strictEqual(sum.mock.callCount(), 0);
      assert.strictEqual(sum(3, 4), 7);
      assert.strictEqual(sum.mock.callCount(), 1);

      const call = sum.mock.calls[0];
      assert.deepStrictEqual(call.arguments, [3, 4]);
      assert.strictEqual(call.result, 7);
      assert.strictEqual(call.error, undefined);

      // Reset the globally tracked mocks.
      mock.reset();
    });
    const assert = require('node:assert');
    const { mock, test } = require('node:test');

    test('spies on a function', () => {
      const sum = mock.fn((a, b) => {
        return a + b;
      });

      assert.strictEqual(sum.mock.callCount(), 0);
      assert.strictEqual(sum(3, 4), 7);
      assert.strictEqual(sum.mock.callCount(), 1);

      const call = sum.mock.calls[0];
      assert.deepStrictEqual(call.arguments, [3, 4]);
      assert.strictEqual(call.result, 7);
      assert.strictEqual(call.error, undefined);

      // Reset the globally tracked mocks.
      mock.reset();
    });
    javascript

The same mocking functionality is also exposed on the `TestContext` object of each test. The following example creates a spy on an object method using the API exposed on the `TestContext`. The benefit of mocking via the test context is that the test runner will automatically restore all mocked functionality once the test finishes.

    test('spies on an object method', (t) => {
      const number = {
        value: 5,
        add(a) {
          return this.value + a;
        },
      };

      t.mock.method(number, 'add');
      assert.strictEqual(number.add.mock.callCount(), 0);
      assert.strictEqual(number.add(3), 8);
      assert.strictEqual(number.add.mock.callCount(), 1);

      const call = number.add.mock.calls[0];

      assert.deepStrictEqual(call.arguments, [3]);
      assert.strictEqual(call.result, 8);
      assert.strictEqual(call.target, undefined);
      assert.strictEqual(call.this, number);
    });
    js

#### Timers#

Mocking timers is a technique commonly used in software testing to simulate and control the behavior of timers, such as `setInterval` and `setTimeout`, without actually waiting for the specified time intervals.

Refer to the `MockTimers` class for a full list of methods and features.

This allows developers to write more reliable and predictable tests for time-dependent functionality.

The example below shows how to mock `setTimeout`. Using `.enable({ apis: ['setTimeout'] });` it will mock the `setTimeout` functions in the node:timers and node:timers/promises modules, as well as from the Node.js global context.

Note: Destructuring functions such as `import { setTimeout } from 'node:timers'` is currently not supported by this API.

    import assert from 'node:assert';
    import { mock, test } from 'node:test';

    test('mocks setTimeout to be executed synchronously without having to actually wait for it', () => {
      const fn = mock.fn();

      // Optionally choose what to mock
      mock.timers.enable({ apis: ['setTimeout'] });
      setTimeout(fn, 9999);
      assert.strictEqual(fn.mock.callCount(), 0);

      // Advance in time
      mock.timers.tick(9999);
      assert.strictEqual(fn.mock.callCount(), 1);

      // Reset the globally tracked mocks.
      mock.timers.reset();

      // If you call reset mock instance, it will also reset timers instance
      mock.reset();
    });
    const assert = require('node:assert');
    const { mock, test } = require('node:test');

    test('mocks setTimeout to be executed synchronously without having to actually wait for it', () => {
      const fn = mock.fn();

      // Optionally choose what to mock
      mock.timers.enable({ apis: ['setTimeout'] });
      setTimeout(fn, 9999);
      assert.strictEqual(fn.mock.callCount(), 0);

      // Advance in time
      mock.timers.tick(9999);
      assert.strictEqual(fn.mock.callCount(), 1);

      // Reset the globally tracked mocks.
      mock.timers.reset();

      // If you call reset mock instance, it will also reset timers instance
      mock.reset();
    });
    javascript

The same mocking functionality is also exposed in the mock property on the `TestContext` object of each test. The benefit of mocking via the test context is that the test runner will automatically restore all mocked timers functionality once the test finishes.

    import assert from 'node:assert';
    import { test } from 'node:test';

    test('mocks setTimeout to be executed synchronously without having to actually wait for it', (context) => {
      const fn = context.mock.fn();

      // Optionally choose what to mock
      context.mock.timers.enable({ apis: ['setTimeout'] });
      setTimeout(fn, 9999);
      assert.strictEqual(fn.mock.callCount(), 0);

      // Advance in time
      context.mock.timers.tick(9999);
      assert.strictEqual(fn.mock.callCount(), 1);
    });
    const assert = require('node:assert');
    const { test } = require('node:test');

    test('mocks setTimeout to be executed synchronously without having to actually wait for it', (context) => {
      const fn = context.mock.fn();

      // Optionally choose what to mock
      context.mock.timers.enable({ apis: ['setTimeout'] });
      setTimeout(fn, 9999);
      assert.strictEqual(fn.mock.callCount(), 0);

      // Advance in time
      context.mock.timers.tick(9999);
      assert.strictEqual(fn.mock.callCount(), 1);
    });
    javascript

#### Dates#

The mock timers API also allows the mocking of the `Date` object. This is a useful feature for testing time-dependent functionality, or to simulate internal calendar functions such as `Date.now()`.

The dates implementation is also part of the `MockTimers` class. Refer to it for a full list of methods and features.

Note: Dates and timers are dependent when mocked together. This means that if you have both the `Date` and `setTimeout` mocked, advancing the time will also advance the mocked date as they simulate a single internal clock.

The example below show how to mock the `Date` object and obtain the current `Date.now()` value.

    import assert from 'node:assert';
    import { test } from 'node:test';

    test('mocks the Date object', (context) => {
      // Optionally choose what to mock
      context.mock.timers.enable({ apis: ['Date'] });
      // If not specified, the initial date will be based on 0 in the UNIX epoch
      assert.strictEqual(Date.now(), 0);

      // Advance in time will also advance the date
      context.mock.timers.tick(9999);
      assert.strictEqual(Date.now(), 9999);
    });
    const assert = require('node:assert');
    const { test } = require('node:test');

    test('mocks the Date object', (context) => {
      // Optionally choose what to mock
      context.mock.timers.enable({ apis: ['Date'] });
      // If not specified, the initial date will be based on 0 in the UNIX epoch
      assert.strictEqual(Date.now(), 0);

      // Advance in time will also advance the date
      context.mock.timers.tick(9999);
      assert.strictEqual(Date.now(), 9999);
    });
    javascript

If there is no initial epoch set, the initial date will be based on 0 in the Unix epoch. This is January 1st, 1970, 00:00:00 UTC. You can set an initial date by passing a `now` property to the `.enable()` method. This value will be used as the initial date for the mocked `Date` object. It can either be a positive integer, or another Date object.

    import assert from 'node:assert';
    import { test } from 'node:test';

    test('mocks the Date object with initial time', (context) => {
      // Optionally choose what to mock
      context.mock.timers.enable({ apis: ['Date'], now: 100 });
      assert.strictEqual(Date.now(), 100);

      // Advance in time will also advance the date
      context.mock.timers.tick(200);
      assert.strictEqual(Date.now(), 300);
    });
    const assert = require('node:assert');
    const { test } = require('node:test');

    test('mocks the Date object with initial time', (context) => {
      // Optionally choose what to mock
      context.mock.timers.enable({ apis: ['Date'], now: 100 });
      assert.strictEqual(Date.now(), 100);

      // Advance in time will also advance the date
      context.mock.timers.tick(200);
      assert.strictEqual(Date.now(), 300);
    });
    javascript

You can use the `.setTime()` method to manually move the mocked date to another time. This method only accepts a positive integer.

Note: This method will not execute any mocked timers that are in the past from the new time.

In the below example we are setting a new time for the mocked date.

    import assert from 'node:assert';
    import { test } from 'node:test';

    test('sets the time of a date object', (context) => {
      // Optionally choose what to mock
      context.mock.timers.enable({ apis: ['Date'], now: 100 });
      assert.strictEqual(Date.now(), 100);

      // Advance in time will also advance the date
      context.mock.timers.setTime(1000);
      context.mock.timers.tick(200);
      assert.strictEqual(Date.now(), 1200);
    });
    const assert = require('node:assert');
    const { test } = require('node:test');

    test('sets the time of a date object', (context) => {
      // Optionally choose what to mock
      context.mock.timers.enable({ apis: ['Date'], now: 100 });
      assert.strictEqual(Date.now(), 100);

      // Advance in time will also advance the date
      context.mock.timers.setTime(1000);
      context.mock.timers.tick(200);
      assert.strictEqual(Date.now(), 1200);
    });
    javascript

Timers scheduled in the past will not run when you call `setTime()`. To execute those timers, you can use the `.tick()` method to move forward from the new time.

    import assert from 'node:assert';
    import { test } from 'node:test';

    test('setTime does not execute timers', (context) => {
      // Optionally choose what to mock
      context.mock.timers.enable({ apis: ['setTimeout', 'Date'] });
      const fn = context.mock.fn();
      setTimeout(fn, 1000);

      context.mock.timers.setTime(800);
      // Timer is not executed as the time is not yet reached
      assert.strictEqual(fn.mock.callCount(), 0);
      assert.strictEqual(Date.now(), 800);

      context.mock.timers.setTime(1200);
      // Timer is still not executed
      assert.strictEqual(fn.mock.callCount(), 0);
      // Advance in time to execute the timer
      context.mock.timers.tick(0);
      assert.strictEqual(fn.mock.callCount(), 1);
      assert.strictEqual(Date.now(), 1200);
    });
    const assert = require('node:assert');
    const { test } = require('node:test');

    test('setTime does not execute timers', (context) => {
      // Optionally choose what to mock
      context.mock.timers.enable({ apis: ['setTimeout', 'Date'] });
      const fn = context.mock.fn();
      setTimeout(fn, 1000);

      context.mock.timers.setTime(800);
      // Timer is not executed as the time is not yet reached
      assert.strictEqual(fn.mock.callCount(), 0);
      assert.strictEqual(Date.now(), 800);

      context.mock.timers.setTime(1200);
      // Timer is still not executed
      assert.strictEqual(fn.mock.callCount(), 0);
      // Advance in time to execute the timer
      context.mock.timers.tick(0);
      assert.strictEqual(fn.mock.callCount(), 1);
      assert.strictEqual(Date.now(), 1200);
    });
    javascript

Using `.runAll()` will execute all timers that are currently in the queue. This will also advance the mocked date to the time of the last timer that was executed as if the time has passed.

    import assert from 'node:assert';
    import { test } from 'node:test';

    test('runs timers as setTime passes ticks', (context) => {
      // Optionally choose what to mock
      context.mock.timers.enable({ apis: ['setTimeout', 'Date'] });
      const fn = context.mock.fn();
      setTimeout(fn, 1000);
      setTimeout(fn, 2000);
      setTimeout(fn, 3000);

      context.mock.timers.runAll();
      // All timers are executed as the time is now reached
      assert.strictEqual(fn.mock.callCount(), 3);
      assert.strictEqual(Date.now(), 3000);
    });
    const assert = require('node:assert');
    const { test } = require('node:test');

    test('runs timers as setTime passes ticks', (context) => {
      // Optionally choose what to mock
      context.mock.timers.enable({ apis: ['setTimeout', 'Date'] });
      const fn = context.mock.fn();
      setTimeout(fn, 1000);
      setTimeout(fn, 2000);
      setTimeout(fn, 3000);

      context.mock.timers.runAll();
      // All timers are executed as the time is now reached
      assert.strictEqual(fn.mock.callCount(), 3);
      assert.strictEqual(Date.now(), 3000);
    });
    javascript

### Snapshot testing#

Added in: v22.3.0
History

Version | Changes
--- | ---
v23.4.0 | Snapshot testing is no longer experimental.

Snapshot tests allow arbitrary values to be serialized into string values and compared against a set of known good values. The known good values are known as snapshots, and are stored in a snapshot file. Snapshot files are managed by the test runner, but are designed to be human readable to aid in debugging. Best practice is for snapshot files to be checked into source control along with your test files.

Snapshot files are generated by starting Node.js with the `--test-update-snapshots` command-line flag. A separate snapshot file is generated for each test file. By default, the snapshot file has the same name as the test file with a `.snapshot` file extension. This behavior can be configured using the `snapshot.setResolveSnapshotPath()` function. Each snapshot assertion corresponds to an export in the snapshot file.

An example snapshot test is shown below. The first time this test is executed, it will fail because the corresponding snapshot file does not exist.

    // test.js
    suite('suite of snapshot tests', () => {
      test('snapshot test', (t) => {
        t.assert.snapshot({ value1: 1, value2: 2 });
        t.assert.snapshot(5);
      });
    });
    js

Generate the snapshot file by running the test file with `--test-update-snapshots`. The test should pass, and a file named `test.js.snapshot` is created in the same directory as the test file. The contents of the snapshot file are shown below. Each snapshot is identified by the full name of test and a counter to differentiate between snapshots in the same test.

    exports[`suite of snapshot tests > snapshot test 1`] = `
    {
      "value1": 1,
      "value2": 2
    }
    `;

    exports[`suite of snapshot tests > snapshot test 2`] = `
    5
    `;
    js

Once the snapshot file is created, run the tests again without the `--test-update-snapshots` flag. The tests should pass now.

### Test reporters#

Added in: v19.6.0, v18.15.0
History

Version | Changes
--- | ---
v23.0.0 | The default reporter on non-TTY stdout is changed from `tap` to `spec`, aligning with TTY stdout.
v19.9.0, v18.17.0 | Reporters are now exposed at `node:test/reporters`.

The `node:test` module supports passing `--test-reporter` flags for the test runner to use a specific reporter.

The following built-reporters are supported:

- `spec` The `spec` reporter outputs the test results in a human-readable format. This is the default reporter.

- `tap` The `tap` reporter outputs the test results in the TAP format.

- `dot` The `dot` reporter outputs the test results in a compact format, where each passing test is represented by a `.`, and each failing test is represented by a `X`.

- `junit` The junit reporter outputs test results in a jUnit XML format

- `lcov` The `lcov` reporter outputs test coverage when used with the `--experimental-test-coverage` flag.

The exact output of these reporters is subject to change between versions of Node.js, and should not be relied on programmatically. If programmatic access to the test runner's output is required, use the events emitted by the `<TestsStream>`.

The reporters are available via the `node:test/reporters` module:

    import { tap, spec, dot, junit, lcov } from 'node:test/reporters';
    const { tap, spec, dot, junit, lcov } = require('node:test/reporters');
    javascript

#### Custom reporters#

`--test-reporter` can be used to specify a path to custom reporter. A custom reporter is a module that exports a value accepted by stream.compose. Reporters should transform events emitted by a `<TestsStream>`

Example of a custom reporter using `<stream.Transform>`:

    import { Transform } from 'node:stream';

    const customReporter = new Transform({
      writableObjectMode: true,
      transform(event, encoding, callback) {
        switch (event.type) {
          case 'test:dequeue':
            callback(null, `test ${event.data.name} dequeued`);
            break;
          case 'test:enqueue':
            callback(null, `test ${event.data.name} enqueued`);
            break;
          case 'test:watch:drained':
            callback(null, 'test watch queue drained');
            break;
          case 'test:watch:restarted':
            callback(null, 'test watch restarted due to file change');
            break;
          case 'test:start':
            callback(null, `test ${event.data.name} started`);
            break;
          case 'test:pass':
            callback(null, `test ${event.data.name} passed`);
            break;
          case 'test:fail':
            callback(null, `test ${event.data.name} failed`);
            break;
          case 'test:plan':
            callback(null, 'test plan');
            break;
          case 'test:diagnostic':
          case 'test:stderr':
          case 'test:stdout':
            callback(null, event.data.message);
            break;
          case 'test:coverage': {
            const { totalLineCount } = event.data.summary.totals;
            callback(null, `total line count: ${totalLineCount}\n`);
            break;
          }
        }
      },
    });

    export default customReporter;
    const { Transform } = require('node:stream');

    const customReporter = new Transform({
      writableObjectMode: true,
      transform(event, encoding, callback) {
        switch (event.type) {
          case 'test:dequeue':
            callback(null, `test ${event.data.name} dequeued`);
            break;
          case 'test:enqueue':
            callback(null, `test ${event.data.name} enqueued`);
            break;
          case 'test:watch:drained':
            callback(null, 'test watch queue drained');
            break;
          case 'test:watch:restarted':
            callback(null, 'test watch restarted due to file change');
            break;
          case 'test:start':
            callback(null, `test ${event.data.name} started`);
            break;
          case 'test:pass':
            callback(null, `test ${event.data.name} passed`);
            break;
          case 'test:fail':
            callback(null, `test ${event.data.name} failed`);
            break;
          case 'test:plan':
            callback(null, 'test plan');
            break;
          case 'test:diagnostic':
          case 'test:stderr':
          case 'test:stdout':
            callback(null, event.data.message);
            break;
          case 'test:coverage': {
            const { totalLineCount } = event.data.summary.totals;
            callback(null, `total line count: ${totalLineCount}\n`);
            break;
          }
        }
      },
    });

    module.exports = customReporter;
    javascript

Example of a custom reporter using a generator function:

    export default async function * customReporter(source) {
      for await (const event of source) {
        switch (event.type) {
          case 'test:dequeue':
            yield `test ${event.data.name} dequeued\n`;
            break;
          case 'test:enqueue':
            yield `test ${event.data.name} enqueued\n`;
            break;
          case 'test:watch:drained':
            yield 'test watch queue drained\n';
            break;
          case 'test:watch:restarted':
            yield 'test watch restarted due to file change\n';
            break;
          case 'test:start':
            yield `test ${event.data.name} started\n`;
            break;
          case 'test:pass':
            yield `test ${event.data.name} passed\n`;
            break;
          case 'test:fail':
            yield `test ${event.data.name} failed\n`;
            break;
          case 'test:plan':
            yield 'test plan\n';
            break;
          case 'test:diagnostic':
          case 'test:stderr':
          case 'test:stdout':
            yield `${event.data.message}\n`;
            break;
          case 'test:coverage': {
            const { totalLineCount } = event.data.summary.totals;
            yield `total line count: ${totalLineCount}\n`;
            break;
          }
        }
      }
    }
    module.exports = async function * customReporter(source) {
      for await (const event of source) {
        switch (event.type) {
          case 'test:dequeue':
            yield `test ${event.data.name} dequeued\n`;
            break;
          case 'test:enqueue':
            yield `test ${event.data.name} enqueued\n`;
            break;
          case 'test:watch:drained':
            yield 'test watch queue drained\n';
            break;
          case 'test:watch:restarted':
            yield 'test watch restarted due to file change\n';
            break;
          case 'test:start':
            yield `test ${event.data.name} started\n`;
            break;
          case 'test:pass':
            yield `test ${event.data.name} passed\n`;
            break;
          case 'test:fail':
            yield `test ${event.data.name} failed\n`;
            break;
          case 'test:plan':
            yield 'test plan\n';
            break;
          case 'test:diagnostic':
          case 'test:stderr':
          case 'test:stdout':
            yield `${event.data.message}\n`;
            break;
          case 'test:coverage': {
            const { totalLineCount } = event.data.summary.totals;
            yield `total line count: ${totalLineCount}\n`;
            break;
          }
        }
      }
    };
    javascript

The value provided to `--test-reporter` should be a string like one used in an `import()` in JavaScript code, or a value provided for `--import`.

#### Multiple reporters#

The `--test-reporter` flag can be specified multiple times to report test results in several formats. In this situation it is required to specify a destination for each reporter using `--test-reporter-destination`. Destination can be `stdout`, `stderr`, or a file path. Reporters and destinations are paired according to the order they were specified.

In the following example, the `spec` reporter will output to `stdout`, and the `dot` reporter will output to `file.txt`:

    node --test-reporter=spec --test-reporter=dot --test-reporter-destination=stdout --test-reporter-destination=file.txt
    bash

When a single reporter is specified, the destination will default to `stdout`, unless a destination is explicitly provided.

### `run([options])`#

Added in: v18.9.0, v16.19.0
History

Version | Changes
--- | ---
v26.2.0 | Added the `testTagFilters` option.
v25.6.0, v24.14.0 | Add the `env` option.
v24.7.0 | Added a rerunFailuresFilePath option.
v23.0.0 | Added the `cwd` option.
v23.0.0, v22.10.0 | Added coverage options.
v22.8.0 | Added the `isolation` option.
v22.6.0 | Added the `globPatterns` option.
v22.0.0, v20.14.0 | Added the `forceExit` option.
v20.1.0, v18.17.0 | Add a testNamePatterns option.

- `options` `<Object>` Configuration options for running tests. The following properties are supported:
  - `concurrency` `<number>` | `<boolean>` If a number is provided, then that many test processes would run in parallel, where each process corresponds to one test file. If `true`, it would run `os.availableParallelism() - 1` test files in parallel. If `false`, it would only run one test file at a time. Default: `false`.
  - `cwd` `<string>` Specifies the current working directory to be used by the test runner. Serves as the base path for resolving files as if running tests from the command line from that directory. Default: `process.cwd()`.
  - `files` `<Array>` An array containing the list of files to run. Default: Same as running tests from the command line.
  - `forceExit` `<boolean>` Configures the test runner to exit the process once all known tests have finished executing even if the event loop would otherwise remain active. Default: `false`.
  - `globPatterns` `<Array>` An array containing the list of glob patterns to match test files. This option cannot be used together with `files`. Default: Same as running tests from the command line.
  - `inspectPort` `<number>` | `<Function>` Sets inspector port of test child process. This can be a number, or a function that takes no arguments and returns a number. If a nullish value is provided, each process gets its own port, incremented from the primary's `process.debugPort`. This option is ignored if the `isolation` option is set to `'none'` as no child processes are spawned. Default: `undefined`.
  - `isolation` `<string>` Configures the type of test isolation. If set to `'process'`, each test file is run in a separate child process. If set to `'none'`, all test files run in the current process. Default: `'process'`.
  - `only` `<boolean>` If truthy, the test context will only run tests that have the `only` option set
  - `setup` `<Function>` A function that accepts the `TestsStream` instance and can be used to setup listeners before any tests are run. Default: `undefined`.
  - `execArgv` `<Array>` An array of CLI flags to pass to the `node` executable when spawning the subprocesses. This option has no effect when `isolation` is `'none`'. Default: `[]`
  - `argv` `<Array>` An array of CLI flags to pass to each test file when spawning the subprocesses. This option has no effect when `isolation` is `'none'`. Default: `[]`.
  - `signal` `<AbortSignal>` Allows aborting an in-progress test execution.
  - `testNamePatterns` `<string>` | `<RegExp>` | `<Array>` A String, RegExp or a RegExp Array, that can be used to only run tests whose name matches the provided pattern. Test name patterns are interpreted as JavaScript regular expressions. For each test that is executed, any corresponding test hooks, such as `beforeEach()`, are also run. Default: `undefined`.
  - `testSkipPatterns` `<string>` | `<RegExp>` | `<Array>` A String, RegExp or a RegExp Array, that can be used to exclude running tests whose name matches the provided pattern. Test name patterns are interpreted as JavaScript regular expressions. For each test that is executed, any corresponding test hooks, such as `beforeEach()`, are also run. Default: `undefined`.
  - `testTagFilters` `<string>` | `<string>`[] A tag name, or an array of tag names, used to filter tests by their declared tags. Tests must contain every listed tag to run. Equivalent to passing `--experimental-test-tag-filter` on the command line. See Test tags. Default: `undefined`.
  - `timeout` `<number>` A number of milliseconds the test execution will fail after. If unspecified, subtests inherit this value from their parent. Default: `Infinity`.
  - `watch` `<boolean>` Whether to run in watch mode or not. Default: `false`.
  - `shard` `<Object>` Running tests in a specific shard. Default: `undefined`.
    - `index` `<number>` is a positive integer between 1 and `<total>` that specifies the index of the shard to run. This option is required.
    - `total` `<number>` is a positive integer that specifies the total number of shards to split the test files to. This option is required.
  - `randomize` `<boolean>` Randomize execution order for test files and queued tests. This option is not supported with `watch: true`. Default: `false`.
  - `randomSeed` `<number>` Seed used when randomizing execution order. If this option is set, runs can replay the same randomized order deterministically, and setting this option also enables randomization. The value must be an integer between `0` and `4294967295`. Default: `undefined`.
  - `rerunFailuresFilePath` `<string>` A file path where the test runner will store the state of the tests to allow rerunning only the failed tests on a next run. see [Rerunning failed tests][] for more information. Default: `undefined`.
  - `coverage` `<boolean>` enable code coverage collection. Default: `false`.
  - `coverageExcludeGlobs` `<string>` | `<Array>` Excludes specific files from code coverage using a glob pattern, which can match both absolute and relative file paths. This property is only applicable when `coverage` was set to `true`. If both `coverageExcludeGlobs` and `coverageIncludeGlobs` are provided, files must meet both criteria to be included in the coverage report. Default: `undefined`.
  - `coverageIncludeGlobs` `<string>` | `<Array>` Includes specific files in code coverage using a glob pattern, which can match both absolute and relative file paths. This property is only applicable when `coverage` was set to `true`. If both `coverageExcludeGlobs` and `coverageIncludeGlobs` are provided, files must meet both criteria to be included in the coverage report. Default: `undefined`.
  - `lineCoverage` `<number>` Require a minimum percent of covered lines. If code coverage does not reach the threshold specified, the process will exit with code `1`. Default: `0`.
  - `branchCoverage` `<number>` Require a minimum percent of covered branches. If code coverage does not reach the threshold specified, the process will exit with code `1`. Default: `0`.
  - `functionCoverage` `<number>` Require a minimum percent of covered functions. If code coverage does not reach the threshold specified, the process will exit with code `1`. Default: `0`.
  - `env` `<Object>` Specify environment variables to be passed along to the test process. This option is not compatible with `isolation='none'`. These variables will override those from the main process, and are not merged with `process.env`. Default: `process.env`.
- Returns: `<TestsStream>`

Note: `shard` is used to horizontally parallelize test running across machines or processes, ideal for large-scale executions across varied environments. It's incompatible with `watch` mode, tailored for rapid code iteration by automatically rerunning tests on file changes.

    import { tap } from 'node:test/reporters';
    import { run } from 'node:test';
    import process from 'node:process';
    import path from 'node:path';

    run({ files: [path.resolve('./tests/test.js')] })
     .on('test:fail', () => {
       process.exitCode = 1;
     })
     .compose(tap)
     .pipe(process.stdout);
    const { tap } = require('node:test/reporters');
    const { run } = require('node:test');
    const path = require('node:path');

    run({ files: [path.resolve('./tests/test.js')] })
     .on('test:fail', () => {
       process.exitCode = 1;
     })
     .compose(tap)
     .pipe(process.stdout);
    javascript

### `suite([name][, options][, fn])`#

Added in: v22.0.0, v20.13.0

- `name` `<string>` The name of the suite, which is displayed when reporting test results. Default: The `name` property of `fn`, or `'<anonymous>'` if `fn` does not have a name.
- `options` `<Object>` Optional configuration options for the suite. This supports the same options as `test([name][, options][, fn])`.
- `fn` `<Function>` | `<AsyncFunction>` The suite function declaring nested tests and suites. The first argument to this function is a `SuiteContext` object. Default: A no-op function.
- Returns: `<Promise>` Immediately fulfilled with `undefined`.

The `suite()` function is imported from the `node:test` module.

### `suite.skip([name][, options][, fn])`#

Added in: v22.0.0, v20.13.0

Shorthand for skipping a suite. This is the same as `suite([name], { skip: true }[, fn])`.

### `suite.todo([name][, options][, fn])`#

Added in: v22.0.0, v20.13.0

Shorthand for marking a suite as `TODO`. This is the same as `suite([name], { todo: true }[, fn])`.

### `suite.only([name][, options][, fn])`#

Added in: v22.0.0, v20.13.0

Shorthand for marking a suite as `only`. This is the same as `suite([name], { only: true }[, fn])`.

### `test([name][, options][, fn])`#

Added in: v18.0.0, v16.17.0
History

Version | Changes
--- | ---
v26.2.0 | Added the `tags` option.
v20.2.0, v18.17.0 | Added the `skip`, `todo`, and `only` shorthands.
v18.8.0, v16.18.0 | Add a `signal` option.
v18.7.0, v16.17.0 | Add a `timeout` option.

- `name` `<string>` The name of the test, which is displayed when reporting test results. Default: The `name` property of `fn`, or `'<anonymous>'` if `fn` does not have a name.
- `options` `<Object>` Configuration options for the test. The following properties are supported:
  - `concurrency` `<number>` | `<boolean>` If a number is provided, then that many tests would run asynchronously (they are still managed by the single-threaded event loop). If `true`, all scheduled asynchronous tests run concurrently within the thread. If `false`, only one test runs at a time. If unspecified, subtests inherit this value from their parent. Default: `false`.
  - `expectFailure` `<boolean>` | `<string>` | `<RegExp>` | `<Function>` | `<Object>` | `<Error>` If truthy, the test is expected to fail. If a non-empty string is provided, that string is displayed in the test results as the reason why the test is expected to fail. If a `<RegExp>` | `<Function>` | `<Object>` | `<Error>` is provided directly (without wrapping in `{ match: … }`), the test passes only if the thrown error matches, following the behavior of `assert.throws`. To provide both a reason and validation, pass an object with `label` (string) and `match` (RegExp, Function, Object, or Error). Default: `false`.
  - `only` `<boolean>` If truthy, and the test context is configured to run `only` tests, then this test will be run. Otherwise, the test is skipped. Default: `false`.
  - `signal` `<AbortSignal>` Allows aborting an in-progress test.
  - `skip` `<boolean>` | `<string>` If truthy, the test is skipped. If a string is provided, that string is displayed in the test results as the reason for skipping the test. Default: `false`.
  - `tags` `<string>`[] An array of string labels associated with the test. Used together with `--experimental-test-tag-filter` to filter which tests run. Tags inherit from suites to nested tests by union. See Test tags. Default: `[]`.
  - `todo` `<boolean>` | `<string>` If truthy, the test marked as `TODO`. If a string is provided, that string is displayed in the test results as the reason why the test is `TODO`. Default: `false`.
  - `timeout` `<number>` A number of milliseconds the test will fail after. If unspecified, subtests inherit this value from their parent. Default: `Infinity`.
  - `plan` `<number>` The number of assertions and subtests expected to be run in the test. If the number of assertions run in the test does not match the number specified in the plan, the test will fail. Default: `undefined`.
- `fn` `<Function>` | `<AsyncFunction>` The function under test. The first argument to this function is a `TestContext` object. If the test uses callbacks, the callback function is passed as the second argument. Default: A no-op function.
- Returns: `<Promise>` Fulfilled with `undefined` once the test completes, or immediately if the test runs within a suite.

The `test()` function is the value imported from the `test` module. Each invocation of this function results in reporting the test to the `<TestsStream>`.

The `TestContext` object passed to the `fn` argument can be used to perform actions related to the current test. Examples include skipping the test, adding additional diagnostic information, or creating subtests.

`test()` returns a `Promise` that fulfills once the test completes. if `test()` is called within a suite, it fulfills immediately. The return value can usually be discarded for top level tests. However, the return value from subtests should be used to prevent the parent test from finishing first and cancelling the subtest as shown in the following example.

    test('top level test', async (t) => {
      // The setTimeout() in the following subtest would cause it to outlive its
      // parent test if 'await' is removed on the next line. Once the parent test
      // completes, it will cancel any outstanding subtests.
      await t.test('longer running subtest', async (t) => {
        return new Promise((resolve, reject) => {
          setTimeout(resolve, 1000);
        });
      });
    });
    js

The `timeout` option can be used to fail the test if it takes longer than `timeout` milliseconds to complete. However, it is not a reliable mechanism for canceling tests because a running test might block the application thread and thus prevent the scheduled cancellation.

### `test.skip([name][, options][, fn])`#

Shorthand for skipping a test, same as `test([name], { skip: true }[, fn])`.

### `test.todo([name][, options][, fn])`#

Shorthand for marking a test as `TODO`, same as `test([name], { todo: true }[, fn])`.

### `test.only([name][, options][, fn])`#

Shorthand for marking a test as `only`, same as `test([name], { only: true }[, fn])`.

### `describe([name][, options][, fn])`#

Alias for `suite()`.

The `describe()` function is imported from the `node:test` module.

### `describe.skip([name][, options][, fn])`#

Shorthand for skipping a suite. This is the same as `describe([name], { skip: true }[, fn])`.

### `describe.todo([name][, options][, fn])`#

Shorthand for marking a suite as `TODO`. This is the same as `describe([name], { todo: true }[, fn])`.

### `describe.only([name][, options][, fn])`#

Added in: v19.8.0, v18.15.0

Shorthand for marking a suite as `only`. This is the same as `describe([name], { only: true }[, fn])`.

### `it([name][, options][, fn])`#

Added in: v18.6.0, v16.17.0
History

Version | Changes
--- | ---
v19.8.0, v18.16.0 | Calling `it()` is now equivalent to calling `test()`.

Alias for `test()`.

The `it()` function is imported from the `node:test` module.

### `it.skip([name][, options][, fn])`#

Shorthand for skipping a test, same as `it([name], { skip: true }[, fn])`.

### `it.todo([name][, options][, fn])`#

Shorthand for marking a test as `TODO`, same as `it([name], { todo: true }[, fn])`.

### `it.only([name][, options][, fn])`#

Added in: v19.8.0, v18.15.0

Shorthand for marking a test as `only`, same as `it([name], { only: true }[, fn])`.

### `before([fn][, options])`#

Added in: v18.8.0, v16.18.0

- `fn` `<Function>` | `<AsyncFunction>` The hook function. If the hook uses callbacks, the callback function is passed as the second argument. Default: A no-op function.
- `options` `<Object>` Configuration options for the hook. The following properties are supported:
  - `signal` `<AbortSignal>` Allows aborting an in-progress hook.
  - `timeout` `<number>` A number of milliseconds the hook will fail after. If unspecified, subtests inherit this value from their parent. Default: `Infinity`.

This function creates a hook that runs before executing a suite.

    describe('tests', async () => {
      before(() => console.log('about to run some test'));
      it('is a subtest', () => {
        // Some relevant assertions here
      });
    });
    js

### `after([fn][, options])`#

Added in: v18.8.0, v16.18.0

- `fn` `<Function>` | `<AsyncFunction>` The hook function. If the hook uses callbacks, the callback function is passed as the second argument. Default: A no-op function.
- `options` `<Object>` Configuration options for the hook. The following properties are supported:
  - `signal` `<AbortSignal>` Allows aborting an in-progress hook.
  - `timeout` `<number>` A number of milliseconds the hook will fail after. If unspecified, subtests inherit this value from their parent. Default: `Infinity`.

This function creates a hook that runs after executing a suite.

    describe('tests', async () => {
      after(() => console.log('finished running tests'));
      it('is a subtest', () => {
        // Some relevant assertion here
      });
    });
    js

Note: The `after` hook is guaranteed to run, even if tests within the suite fail.

### `beforeEach([fn][, options])`#

Added in: v18.8.0, v16.18.0

- `fn` `<Function>` | `<AsyncFunction>` The hook function. If the hook uses callbacks, the callback function is passed as the second argument. Default: A no-op function.
- `options` `<Object>` Configuration options for the hook. The following properties are supported:
  - `signal` `<AbortSignal>` Allows aborting an in-progress hook.
  - `timeout` `<number>` A number of milliseconds the hook will fail after. If unspecified, subtests inherit this value from their parent. Default: `Infinity`.

This function creates a hook that runs before each test in the current suite.

    describe('tests', async () => {
      beforeEach(() => console.log('about to run a test'));
      it('is a subtest', () => {
        // Some relevant assertion here
      });
    });
    js

### `afterEach([fn][, options])`#

Added in: v18.8.0, v16.18.0

- `fn` `<Function>` | `<AsyncFunction>` The hook function. If the hook uses callbacks, the callback function is passed as the second argument. Default: A no-op function.
- `options` `<Object>` Configuration options for the hook. The following properties are supported:
  - `signal` `<AbortSignal>` Allows aborting an in-progress hook.
  - `timeout` `<number>` A number of milliseconds the hook will fail after. If unspecified, subtests inherit this value from their parent. Default: `Infinity`.

This function creates a hook that runs after each test in the current suite. The `afterEach()` hook is run even if the test fails.

    describe('tests', async () => {
      afterEach(() => console.log('finished running a test'));
      it('is a subtest', () => {
        // Some relevant assertion here
      });
    });
    js

### `assert`#

Added in: v23.7.0, v22.14.0

An object whose methods are used to configure available assertions on the `TestContext` objects in the current process. The methods from `node:assert` and snapshot testing functions are available by default.

It is possible to apply the same configuration to all files by placing common configuration code in a module preloaded with `--require` or `--import`.

#### `assert.register(name, fn)`#

Added in: v23.7.0, v22.14.0

Defines a new assertion function with the provided name and function. If an assertion already exists with the same name, it is overwritten.

### `snapshot`#

Added in: v22.3.0

An object whose methods are used to configure default snapshot settings in the current process. It is possible to apply the same configuration to all files by placing common configuration code in a module preloaded with `--require` or `--import`.

#### `snapshot.setDefaultSnapshotSerializers(serializers)`#

Added in: v22.3.0

- `serializers` `<Array>` An array of synchronous functions used as the default serializers for snapshot tests.

This function is used to customize the default serialization mechanism used by the test runner. By default, the test runner performs serialization by calling `JSON.stringify(value, null, 2)` on the provided value. `JSON.stringify()` does have limitations regarding circular structures and supported data types. If a more robust serialization mechanism is required, this function should be used.

#### `snapshot.setResolveSnapshotPath(fn)`#

Added in: v22.3.0

- `fn` `<Function>` A function used to compute the location of the snapshot file. The function receives the path of the test file as its only argument. If the test is not associated with a file (for example in the REPL), the input is undefined. `fn()` must return a string specifying the location of the snapshot snapshot file.

This function is used to customize the location of the snapshot file used for snapshot testing. By default, the snapshot filename is the same as the entry point filename with a `.snapshot` file extension.

### Class: `MockFunctionContext`#

Added in: v19.1.0, v18.13.0

The `MockFunctionContext` class is used to inspect or manipulate the behavior of mocks created via the `MockTracker` APIs.

#### `ctx.calls`#

Added in: v19.1.0, v18.13.0

- Type: `<Array>`

A getter that returns a copy of the internal array used to track calls to the mock. Each entry in the array is an object with the following properties.

- `arguments` `<Array>` An array of the arguments passed to the mock function.
- `error` `<any>` If the mocked function threw then this property contains the thrown value. Default: `undefined`.
- `result` `<any>` The value returned by the mocked function.
- `stack` `<Error>` An `Error` object whose stack can be used to determine the callsite of the mocked function invocation.
- `target` `<Function>` | `<undefined>` If the mocked function is a constructor, this field contains the class being constructed. Otherwise this will be `undefined`.
- `this` `<any>` The mocked function's `this` value.

#### `ctx.callCount()`#

Added in: v19.1.0, v18.13.0

- Returns: `<integer>` The number of times that this mock has been invoked.

This function returns the number of times that this mock has been invoked. This function is more efficient than checking `ctx.calls.length` because `ctx.calls` is a getter that creates a copy of the internal call tracking array.

#### `ctx.mockImplementation(implementation)`#

Added in: v19.1.0, v18.13.0

- `implementation` `<Function>` | `<AsyncFunction>` The function to be used as the mock's new implementation.

This function is used to change the behavior of an existing mock.

The following example creates a mock function using `t.mock.fn()`, calls the mock function, and then changes the mock implementation to a different function.

    test('changes a mock behavior', (t) => {
      let cnt = 0;

      function addOne() {
        cnt++;
        return cnt;
      }

      function addTwo() {
        cnt += 2;
        return cnt;
      }

      const fn = t.mock.fn(addOne);

      assert.strictEqual(fn(), 1);
      fn.mock.mockImplementation(addTwo);
      assert.strictEqual(fn(), 3);
      assert.strictEqual(fn(), 5);
    });
    js

#### `ctx.mockImplementationOnce(implementation[, onCall])`#

Added in: v19.1.0, v18.13.0

- `implementation` `<Function>` | `<AsyncFunction>` The function to be used as the mock's implementation for the invocation number specified by `onCall`.
- `onCall` `<integer>` The invocation number that will use `implementation`. If the specified invocation has already occurred then an exception is thrown. Default: The number of the next invocation.

This function is used to change the behavior of an existing mock for a single invocation. Once invocation `onCall` has occurred, the mock will revert to whatever behavior it would have used had `mockImplementationOnce()` not been called.

The following example creates a mock function using `t.mock.fn()`, calls the mock function, changes the mock implementation to a different function for the next invocation, and then resumes its previous behavior.

    test('changes a mock behavior once', (t) => {
      let cnt = 0;

      function addOne() {
        cnt++;
        return cnt;
      }

      function addTwo() {
        cnt += 2;
        return cnt;
      }

      const fn = t.mock.fn(addOne);

      assert.strictEqual(fn(), 1);
      fn.mock.mockImplementationOnce(addTwo);
      assert.strictEqual(fn(), 3);
      assert.strictEqual(fn(), 4);
    });
    js

#### `ctx.resetCalls()`#

Added in: v19.3.0, v18.13.0

Resets the call history of the mock function.

#### `ctx.restore()`#

Added in: v19.1.0, v18.13.0

Resets the implementation of the mock function to its original behavior. The mock can still be used after calling this function.

### Class: `MockModuleContext`#

Added in: v22.3.0, v20.18.0

Stability: 1.0 - Early development

The `MockModuleContext` class is used to manipulate the behavior of module mocks created via the `MockTracker` APIs.

#### `ctx.restore()`#

Added in: v22.3.0, v20.18.0

Resets the implementation of the mock module.

### Class: `MockPropertyContext`#

Added in: v24.3.0, v22.20.0

The `MockPropertyContext` class is used to inspect or manipulate the behavior of property mocks created via the `MockTracker` APIs.

#### `ctx.accesses`#

- Type: `<Array>`

A getter that returns a copy of the internal array used to track accesses (get/set) to the mocked property. Each entry in the array is an object with the following properties:

- `type` `<string>` Either `'get'` or `'set'`, indicating the type of access.
- `value` `<any>` The value that was read (for `'get'`) or written (for `'set'`).
- `stack` `<Error>` An `Error` object whose stack can be used to determine the callsite of the mocked function invocation.

#### `ctx.accessCount()`#

- Returns: `<integer>` The number of times that the property was accessed (read or written).

This function returns the number of times that the property was accessed. This function is more efficient than checking `ctx.accesses.length` because `ctx.accesses` is a getter that creates a copy of the internal access tracking array.

#### `ctx.mockImplementation(value)`#

- `value` `<any>` The new value to be set as the mocked property value.

This function is used to change the value returned by the mocked property getter.

#### `ctx.mockImplementationOnce(value[, onAccess])`#

- `value` `<any>` The value to be used as the mock's implementation for the invocation number specified by `onAccess`.
- `onAccess` `<integer>` The invocation number that will use `value`. If the specified invocation has already occurred then an exception is thrown. Default: The number of the next invocation.

This function is used to change the behavior of an existing mock for a single invocation. Once invocation `onAccess` has occurred, the mock will revert to whatever behavior it would have used had `mockImplementationOnce()` not been called.

The following example creates a mock function using `t.mock.property()`, calls the mock property, changes the mock implementation to a different value for the next invocation, and then resumes its previous behavior.

    test('changes a mock behavior once', (t) => {
      const obj = { foo: 1 };

      const prop = t.mock.property(obj, 'foo', 5);

      assert.strictEqual(obj.foo, 5);
      prop.mock.mockImplementationOnce(25);
      assert.strictEqual(obj.foo, 25);
      assert.strictEqual(obj.foo, 5);
    });
    js

##### Caveat#

For consistency with the rest of the mocking API, this function treats both property gets and sets as accesses. If a property set occurs at the same access index, the "once" value will be consumed by the set operation, and the mocked property value will be changed to the "once" value. This may lead to unexpected behavior if you intend the "once" value to only be used for a get operation.

#### `ctx.resetAccesses()`#

Resets the access history of the mocked property.

#### `ctx.restore()`#

Resets the implementation of the mock property to its original behavior. The mock can still be used after calling this function.

### Class: `MockTracker`#

Added in: v19.1.0, v18.13.0

The `MockTracker` class is used to manage mocking functionality. The test runner module provides a top level `mock` export which is a `MockTracker` instance. Each test also provides its own `MockTracker` instance via the test context's `mock` property.

#### `mock.fn([original[, implementation]][, options])`#

Added in: v19.1.0, v18.13.0

- `original` `<Function>` | `<AsyncFunction>` An optional function to create a mock on. Default: A no-op function.
- `implementation` `<Function>` | `<AsyncFunction>` An optional function used as the mock implementation for `original`. This is useful for creating mocks that exhibit one behavior for a specified number of calls and then restore the behavior of `original`. Default: The function specified by `original`.
- `options` `<Object>` Optional configuration options for the mock function. The following properties are supported:
  - `times` `<integer>` The number of times that the mock will use the behavior of `implementation`. Once the mock function has been called `times` times, it will automatically restore the behavior of `original`. This value must be an integer greater than zero. Default: `Infinity`.
- Returns: `<Proxy>` The mocked function. The mocked function contains a special `mock` property, which is an instance of `MockFunctionContext`, and can be used for inspecting and changing the behavior of the mocked function.

This function is used to create a mock function.

The following example creates a mock function that increments a counter by one on each invocation. The `times` option is used to modify the mock behavior such that the first two invocations add two to the counter instead of one.

    test('mocks a counting function', (t) => {
      let cnt = 0;

      function addOne() {
        cnt++;
        return cnt;
      }

      function addTwo() {
        cnt += 2;
        return cnt;
      }

      const fn = t.mock.fn(addOne, addTwo, { times: 2 });

      assert.strictEqual(fn(), 2);
      assert.strictEqual(fn(), 4);
      assert.strictEqual(fn(), 5);
      assert.strictEqual(fn(), 6);
    });
    js

#### `mock.getter(object, methodName[, implementation][, options])`#

Added in: v19.3.0, v18.13.0

This function is syntax sugar for `MockTracker.method` with `options.getter` set to `true`.

#### `mock.method(object, methodName[, implementation][, options])`#

Added in: v19.1.0, v18.13.0

- `object` `<Object>` The object whose method is being mocked.
- `methodName` `<string>` | `<symbol>` The identifier of the method on `object` to mock. If `object[methodName]` is not a function, an error is thrown.
- `implementation` `<Function>` | `<AsyncFunction>` An optional function used as the mock implementation for `object[methodName]`. Default: The original method specified by `object[methodName]`.
- `options` `<Object>` Optional configuration options for the mock method. The following properties are supported:
  - `getter` `<boolean>` If `true`, `object[methodName]` is treated as a getter. This option cannot be used with the `setter` option. Default: false.
  - `setter` `<boolean>` If `true`, `object[methodName]` is treated as a setter. This option cannot be used with the `getter` option. Default: false.
  - `times` `<integer>` The number of times that the mock will use the behavior of `implementation`. Once the mocked method has been called `times` times, it will automatically restore the original behavior. This value must be an integer greater than zero. Default: `Infinity`.
- Returns: `<Proxy>` The mocked method. The mocked method contains a special `mock` property, which is an instance of `MockFunctionContext`, and can be used for inspecting and changing the behavior of the mocked method.

This function is used to create a mock on an existing object method. The following example demonstrates how a mock is created on an existing object method.

    test('spies on an object method', (t) => {
      const number = {
        value: 5,
        subtract(a) {
          return this.value - a;
        },
      };

      t.mock.method(number, 'subtract');
      assert.strictEqual(number.subtract.mock.callCount(), 0);
      assert.strictEqual(number.subtract(3), 2);
      assert.strictEqual(number.subtract.mock.callCount(), 1);

      const call = number.subtract.mock.calls[0];

      assert.deepStrictEqual(call.arguments, [3]);
      assert.strictEqual(call.result, 2);
      assert.strictEqual(call.error, undefined);
      assert.strictEqual(call.target, undefined);
      assert.strictEqual(call.this, number);
    });
    js

#### `mock.module(specifier[, options])`#

Added in: v22.3.0, v20.18.0
History

Version | Changes
--- | ---
v24.0.0, v22.17.0 | Support JSON modules.

Stability: 1.0 - Early development

- `specifier` `<string>` | `<URL>` A string identifying the module to mock.
- `options` `<Object>` Optional configuration options for the mock module. The following properties are supported:
  - `cache` `<boolean>` If `false`, each call to `require()` or `import()` generates a new mock module. If `true`, subsequent calls will return the same module mock, and the mock module is inserted into the CommonJS cache. Default: false.
  - `exports` `<Object>` Optional mocked exports. The `default` property, if provided, is used as the mocked module's default export. All other own enumerable properties are used as named exports. This option cannot be used with `defaultExport` or `namedExports`.
    - If the mock is a CommonJS or builtin module, `exports.default` is used as the value of `module.exports`.
    - If `exports.default` is not provided for a CommonJS or builtin mock, `module.exports` defaults to an empty object.
    - If named exports are provided with a non-object default export, the mock throws an exception when used as a CommonJS or builtin module.
  - `defaultExport` `<any>` An optional value used as the mocked module's default export. If this value is not provided, ESM mocks do not include a default export. If the mock is a CommonJS or builtin module, this setting is used as the value of `module.exports`. If this value is not provided, CJS and builtin mocks use an empty object as the value of `module.exports`. This option cannot be used with `options.exports`. This option is deprecated and will be removed in a later version. Prefer `options.exports.default`.
  - `namedExports` `<Object>` An optional object whose keys and values are used to create the named exports of the mock module. If the mock is a CommonJS or builtin module, these values are copied onto `module.exports`. Therefore, if a mock is created with both named exports and a non-object default export, the mock will throw an exception when used as a CJS or builtin module. This option cannot be used with `options.exports`. This option is deprecated and will be removed in a later version. Prefer `options.exports`.
- Returns: `<MockModuleContext>` An object that can be used to manipulate the mock.

This function is used to mock the exports of ECMAScript modules, CommonJS modules, JSON modules, and Node.js builtin modules. Any references to the original module prior to mocking are not impacted. In order to enable module mocking, Node.js must be started with the `--experimental-test-module-mocks` command-line flag.

Note: module customization hooks registered via the synchronous API effect resolution of the `specifier` provided to `mock.module`. Customization hooks registered via the asynchronous API are currently ignored (because the test runner's loader is synchronous, and node does not support multi-chain / cross-chain loading).

The following example demonstrates how a mock is created for a module.

    test('mocks a builtin module in both module systems', async (t) => {
      // Create a mock of 'node:readline' with a named export named 'foo', which
      // does not exist in the original 'node:readline' module.
      const mock = t.mock.module('node:readline', {
        exports: { foo: () => 42 },
      });

      let esmImpl = await import('node:readline');
      let cjsImpl = require('node:readline');

      // cursorTo() is an export of the original 'node:readline' module.
      assert.strictEqual(esmImpl.cursorTo, undefined);
      assert.strictEqual(cjsImpl.cursorTo, undefined);
      assert.strictEqual(esmImpl.foo(), 42);
      assert.strictEqual(cjsImpl.foo(), 42);

      mock.restore();

      // The mock is restored, so the original builtin module is returned.
      esmImpl = await import('node:readline');
      cjsImpl = require('node:readline');

      assert.strictEqual(typeof esmImpl.cursorTo, 'function');
      assert.strictEqual(typeof cjsImpl.cursorTo, 'function');
      assert.strictEqual(esmImpl.foo, undefined);
      assert.strictEqual(cjsImpl.foo, undefined);
    });
    js

#### `mock.property(object, propertyName[, value])`#

Added in: v24.3.0, v22.20.0

- `object` `<Object>` The object whose value is being mocked.
- `propertyName` `<string>` | `<symbol>` The identifier of the property on `object` to mock.
- `value` `<any>` An optional value used as the mock value for `object[propertyName]`. Default: The original property value.
- Returns: `<Proxy>` A proxy to the mocked object. The mocked object contains a special `mock` property, which is an instance of `MockPropertyContext`, and can be used for inspecting and changing the behavior of the mocked property.

Creates a mock for a property value on an object. This allows you to track and control access to a specific property, including how many times it is read (getter) or written (setter), and to restore the original value after mocking.

    test('mocks a property value', (t) => {
      const obj = { foo: 42 };
      const prop = t.mock.property(obj, 'foo', 100);

      assert.strictEqual(obj.foo, 100);
      assert.strictEqual(prop.mock.accessCount(), 1);
      assert.strictEqual(prop.mock.accesses[0].type, 'get');
      assert.strictEqual(prop.mock.accesses[0].value, 100);

      obj.foo = 200;
      assert.strictEqual(prop.mock.accessCount(), 2);
      assert.strictEqual(prop.mock.accesses[1].type, 'set');
      assert.strictEqual(prop.mock.accesses[1].value, 200);

      prop.mock.restore();
      assert.strictEqual(obj.foo, 42);
    });
    js

#### `mock.reset()`#

Added in: v19.1.0, v18.13.0

This function restores the default behavior of all mocks that were previously created by this `MockTracker` and disassociates the mocks from the `MockTracker` instance. Once disassociated, the mocks can still be used, but the `MockTracker` instance can no longer be used to reset their behavior or otherwise interact with them.

After each test completes, this function is called on the test context's `MockTracker`. If the global `MockTracker` is used extensively, calling this function manually is recommended.

#### `mock.restoreAll()`#

Added in: v19.1.0, v18.13.0

This function restores the default behavior of all mocks that were previously created by this `MockTracker`. Unlike `mock.reset()`, `mock.restoreAll()` does not disassociate the mocks from the `MockTracker` instance.

#### `mock.setter(object, methodName[, implementation][, options])`#

Added in: v19.3.0, v18.13.0

This function is syntax sugar for `MockTracker.method` with `options.setter` set to `true`.

### Class: `MockTimers`#

Added in: v20.4.0, v18.19.0
History

Version | Changes
--- | ---
v23.1.0 | The Mock Timers is now stable.

Mocking timers is a technique commonly used in software testing to simulate and control the behavior of timers, such as `setInterval` and `setTimeout`, without actually waiting for the specified time intervals.

MockTimers is also able to mock the `Date` object.

The `MockTracker` provides a top-level `timers` export which is a `MockTimers` instance.

#### `timers.enable([enableOptions])`#

Added in: v20.4.0, v18.19.0
History

Version | Changes
--- | ---
v21.2.0, v20.11.0 | Updated parameters to be an option object with available APIs and the default initial epoch.

Enables timer mocking for the specified timers.

- `enableOptions` `<Object>` Optional configuration options for enabling timer mocking. The following properties are supported:
  - `apis` `<Array>` An optional array containing the timers to mock. The currently supported timer values are `'setInterval'`, `'setTimeout'`, `'setImmediate'`, and `'Date'`. Default: `['setInterval', 'setTimeout', 'setImmediate', 'Date']`. If no array is provided, all time related APIs (`'setInterval'`, `'clearInterval'`, `'setTimeout'`, `'clearTimeout'`, `'setImmediate'`, `'clearImmediate'`, and `'Date'`) will be mocked by default.
  - `now` `<number>` | `<Date>` An optional number or Date object representing the initial time (in milliseconds) to use as the value for `Date.now()`. Default: `0`.

Note: When you enable mocking for a specific timer, its associated clear function will also be implicitly mocked.

Note: Mocking `Date` will affect the behavior of the mocked timers as they use the same internal clock.

Example usage without setting initial time:

    import { mock } from 'node:test';
    mock.timers.enable({ apis: ['setInterval'] });
    const { mock } = require('node:test');
    mock.timers.enable({ apis: ['setInterval'] });
    javascript

The above example enables mocking for the `setInterval` timer and implicitly mocks the `clearInterval` function. Only the `setInterval` and `clearInterval` functions from node:timers, node:timers/promises, and `globalThis` will be mocked.

Example usage with initial time set

    import { mock } from 'node:test';
    mock.timers.enable({ apis: ['Date'], now: 1000 });
    const { mock } = require('node:test');
    mock.timers.enable({ apis: ['Date'], now: 1000 });
    javascript

Example usage with initial Date object as time set

    import { mock } from 'node:test';
    mock.timers.enable({ apis: ['Date'], now: new Date() });
    const { mock } = require('node:test');
    mock.timers.enable({ apis: ['Date'], now: new Date() });
    javascript

Alternatively, if you call `mock.timers.enable()` without any parameters:

All timers (`'setInterval'`, `'clearInterval'`, `'setTimeout'`, `'clearTimeout'`, `'setImmediate'`, and `'clearImmediate'`) will be mocked. The `setInterval`, `clearInterval`, `setTimeout`, `clearTimeout`, `setImmediate`, and `clearImmediate` functions from `node:timers`, `node:timers/promises`, and `globalThis` will be mocked. As well as the global `Date` object.

#### `timers.reset()`#

Added in: v20.4.0, v18.19.0

This function restores the default behavior of all mocks that were previously created by this `MockTimers` instance and disassociates the mocks from the `MockTracker` instance.

Note: After each test completes, this function is called on the test context's `MockTracker`.

    import { mock } from 'node:test';
    mock.timers.reset();
    const { mock } = require('node:test');
    mock.timers.reset();
    javascript

#### `timers[Symbol.dispose]()`#

Calls `timers.reset()`.

#### `timers.tick([milliseconds])`#

Added in: v20.4.0, v18.19.0

Advances time for all mocked timers.

- `milliseconds` `<number>` The amount of time, in milliseconds, to advance the timers. Default: `1`.

Note: This diverges from how `setTimeout` in Node.js behaves and accepts only positive numbers. In Node.js, `setTimeout` with negative numbers is only supported for web compatibility reasons.

The following example mocks a `setTimeout` function and by using `.tick` advances in time triggering all pending timers.

    import assert from 'node:assert';
    import { test } from 'node:test';

    test('mocks setTimeout to be executed synchronously without having to actually wait for it', (context) => {
      const fn = context.mock.fn();

      context.mock.timers.enable({ apis: ['setTimeout'] });

      setTimeout(fn, 9999);

      assert.strictEqual(fn.mock.callCount(), 0);

      // Advance in time
      context.mock.timers.tick(9999);

      assert.strictEqual(fn.mock.callCount(), 1);
    });
    const assert = require('node:assert');
    const { test } = require('node:test');

    test('mocks setTimeout to be executed synchronously without having to actually wait for it', (context) => {
      const fn = context.mock.fn();
      context.mock.timers.enable({ apis: ['setTimeout'] });

      setTimeout(fn, 9999);
      assert.strictEqual(fn.mock.callCount(), 0);

      // Advance in time
      context.mock.timers.tick(9999);

      assert.strictEqual(fn.mock.callCount(), 1);
    });
    javascript

Alternatively, the `.tick` function can be called many times

    import assert from 'node:assert';
    import { test } from 'node:test';

    test('mocks setTimeout to be executed synchronously without having to actually wait for it', (context) => {
      const fn = context.mock.fn();
      context.mock.timers.enable({ apis: ['setTimeout'] });
      const nineSecs = 9000;
      setTimeout(fn, nineSecs);

      const threeSeconds = 3000;
      context.mock.timers.tick(threeSeconds);
      context.mock.timers.tick(threeSeconds);
      context.mock.timers.tick(threeSeconds);

      assert.strictEqual(fn.mock.callCount(), 1);
    });
    const assert = require('node:assert');
    const { test } = require('node:test');

    test('mocks setTimeout to be executed synchronously without having to actually wait for it', (context) => {
      const fn = context.mock.fn();
      context.mock.timers.enable({ apis: ['setTimeout'] });
      const nineSecs = 9000;
      setTimeout(fn, nineSecs);

      const threeSeconds = 3000;
      context.mock.timers.tick(threeSeconds);
      context.mock.timers.tick(threeSeconds);
      context.mock.timers.tick(threeSeconds);

      assert.strictEqual(fn.mock.callCount(), 1);
    });
    javascript

Advancing time using `.tick` will also advance the time for any `Date` object created after the mock was enabled (if `Date` was also set to be mocked).

    import assert from 'node:assert';
    import { test } from 'node:test';

    test('mocks setTimeout to be executed synchronously without having to actually wait for it', (context) => {
      const fn = context.mock.fn();

      context.mock.timers.enable({ apis: ['setTimeout', 'Date'] });
      setTimeout(fn, 9999);

      assert.strictEqual(fn.mock.callCount(), 0);
      assert.strictEqual(Date.now(), 0);

      // Advance in time
      context.mock.timers.tick(9999);
      assert.strictEqual(fn.mock.callCount(), 1);
      assert.strictEqual(Date.now(), 9999);
    });
    const assert = require('node:assert');
    const { test } = require('node:test');

    test('mocks setTimeout to be executed synchronously without having to actually wait for it', (context) => {
      const fn = context.mock.fn();
      context.mock.timers.enable({ apis: ['setTimeout', 'Date'] });

      setTimeout(fn, 9999);
      assert.strictEqual(fn.mock.callCount(), 0);
      assert.strictEqual(Date.now(), 0);

      // Advance in time
      context.mock.timers.tick(9999);
      assert.strictEqual(fn.mock.callCount(), 1);
      assert.strictEqual(Date.now(), 9999);
    });
    javascript

##### Using clear functions#

As mentioned, all clear functions from timers (`clearTimeout`, `clearInterval`,and `clearImmediate`) are implicitly mocked. Take a look at this example using `setTimeout`:

    import assert from 'node:assert';
    import { test } from 'node:test';

    test('mocks setTimeout to be executed synchronously without having to actually wait for it', (context) => {
      const fn = context.mock.fn();

      // Optionally choose what to mock
      context.mock.timers.enable({ apis: ['setTimeout'] });
      const id = setTimeout(fn, 9999);

      // Implicitly mocked as well
      clearTimeout(id);
      context.mock.timers.tick(9999);

      // As that setTimeout was cleared the mock function will never be called
      assert.strictEqual(fn.mock.callCount(), 0);
    });
    const assert = require('node:assert');
    const { test } = require('node:test');

    test('mocks setTimeout to be executed synchronously without having to actually wait for it', (context) => {
      const fn = context.mock.fn();

      // Optionally choose what to mock
      context.mock.timers.enable({ apis: ['setTimeout'] });
      const id = setTimeout(fn, 9999);

      // Implicitly mocked as well
      clearTimeout(id);
      context.mock.timers.tick(9999);

      // As that setTimeout was cleared the mock function will never be called
      assert.strictEqual(fn.mock.callCount(), 0);
    });
    javascript

##### Working with Node.js timers modules#

Once you enable mocking timers, node:timers, node:timers/promises modules, and timers from the Node.js global context are enabled:

Note: Destructuring functions such as `import { setTimeout } from 'node:timers'` is currently not supported by this API.

    import assert from 'node:assert';
    import { test } from 'node:test';
    import nodeTimers from 'node:timers';
    import nodeTimersPromises from 'node:timers/promises';

    test('mocks setTimeout to be executed synchronously without having to actually wait for it', async (context) => {
      const globalTimeoutObjectSpy = context.mock.fn();
      const nodeTimerSpy = context.mock.fn();
      const nodeTimerPromiseSpy = context.mock.fn();

      // Optionally choose what to mock
      context.mock.timers.enable({ apis: ['setTimeout'] });
      setTimeout(globalTimeoutObjectSpy, 9999);
      nodeTimers.setTimeout(nodeTimerSpy, 9999);

      const promise = nodeTimersPromises.setTimeout(9999).then(nodeTimerPromiseSpy);

      // Advance in time
      context.mock.timers.tick(9999);
      assert.strictEqual(globalTimeoutObjectSpy.mock.callCount(), 1);
      assert.strictEqual(nodeTimerSpy.mock.callCount(), 1);
      await promise;
      assert.strictEqual(nodeTimerPromiseSpy.mock.callCount(), 1);
    });
    const assert = require('node:assert');
    const { test } = require('node:test');
    const nodeTimers = require('node:timers');
    const nodeTimersPromises = require('node:timers/promises');

    test('mocks setTimeout to be executed synchronously without having to actually wait for it', async (context) => {
      const globalTimeoutObjectSpy = context.mock.fn();
      const nodeTimerSpy = context.mock.fn();
      const nodeTimerPromiseSpy = context.mock.fn();

      // Optionally choose what to mock
      context.mock.timers.enable({ apis: ['setTimeout'] });
      setTimeout(globalTimeoutObjectSpy, 9999);
      nodeTimers.setTimeout(nodeTimerSpy, 9999);

      const promise = nodeTimersPromises.setTimeout(9999).then(nodeTimerPromiseSpy);

      // Advance in time
      context.mock.timers.tick(9999);
      assert.strictEqual(globalTimeoutObjectSpy.mock.callCount(), 1);
      assert.strictEqual(nodeTimerSpy.mock.callCount(), 1);
      await promise;
      assert.strictEqual(nodeTimerPromiseSpy.mock.callCount(), 1);
    });
    javascript

In Node.js, `setInterval` from node:timers/promises is an `AsyncGenerator` and is also supported by this API:

    import assert from 'node:assert';
    import { test } from 'node:test';
    import nodeTimersPromises from 'node:timers/promises';
    test('should tick five times testing a real use case', async (context) => {
      context.mock.timers.enable({ apis: ['setInterval'] });

      const expectedIterations = 3;
      const interval = 1000;
      const startedAt = Date.now();
      async function run() {
        const times = [];
        for await (const time of nodeTimersPromises.setInterval(interval, startedAt)) {
          times.push(time);
          if (times.length === expectedIterations) break;
        }
        return times;
      }

      const r = run();
      context.mock.timers.tick(interval);
      context.mock.timers.tick(interval);
      context.mock.timers.tick(interval);

      const timeResults = await r;
      assert.strictEqual(timeResults.length, expectedIterations);
      for (let it = 1; it < expectedIterations; it++) {
        assert.strictEqual(timeResults[it - 1], startedAt + (interval * it));
      }
    });
    const assert = require('node:assert');
    const { test } = require('node:test');
    const nodeTimersPromises = require('node:timers/promises');
    test('should tick five times testing a real use case', async (context) => {
      context.mock.timers.enable({ apis: ['setInterval'] });

      const expectedIterations = 3;
      const interval = 1000;
      const startedAt = Date.now();
      async function run() {
        const times = [];
        for await (const time of nodeTimersPromises.setInterval(interval, startedAt)) {
          times.push(time);
          if (times.length === expectedIterations) break;
        }
        return times;
      }

      const r = run();
      context.mock.timers.tick(interval);
      context.mock.timers.tick(interval);
      context.mock.timers.tick(interval);

      const timeResults = await r;
      assert.strictEqual(timeResults.length, expectedIterations);
      for (let it = 1; it < expectedIterations; it++) {
        assert.strictEqual(timeResults[it - 1], startedAt + (interval * it));
      }
    });
    javascript

#### `timers.runAll()`#

Added in: v20.4.0, v18.19.0

Triggers all pending mocked timers immediately. If the `Date` object is also mocked, it will also advance the `Date` object to the furthest timer's time.

The example below triggers all pending timers immediately, causing them to execute without any delay.

    import assert from 'node:assert';
    import { test } from 'node:test';

    test('runAll functions following the given order', (context) => {
      context.mock.timers.enable({ apis: ['setTimeout', 'Date'] });
      const results = [];
      setTimeout(() => results.push(1), 9999);

      // Notice that if both timers have the same timeout,
      // the order of execution is guaranteed
      setTimeout(() => results.push(3), 8888);
      setTimeout(() => results.push(2), 8888);

      assert.deepStrictEqual(results, []);

      context.mock.timers.runAll();
      assert.deepStrictEqual(results, [3, 2, 1]);
      // The Date object is also advanced to the furthest timer's time
      assert.strictEqual(Date.now(), 9999);
    });
    const assert = require('node:assert');
    const { test } = require('node:test');

    test('runAll functions following the given order', (context) => {
      context.mock.timers.enable({ apis: ['setTimeout', 'Date'] });
      const results = [];
      setTimeout(() => results.push(1), 9999);

      // Notice that if both timers have the same timeout,
      // the order of execution is guaranteed
      setTimeout(() => results.push(3), 8888);
      setTimeout(() => results.push(2), 8888);

      assert.deepStrictEqual(results, []);

      context.mock.timers.runAll();
      assert.deepStrictEqual(results, [3, 2, 1]);
      // The Date object is also advanced to the furthest timer's time
      assert.strictEqual(Date.now(), 9999);
    });
    javascript

Note: The `runAll()` function is specifically designed for triggering timers in the context of timer mocking. It does not have any effect on real-time system clocks or actual timers outside of the mocking environment.

#### `timers.setTime(milliseconds)`#

Added in: v21.2.0, v20.11.0

Sets the current Unix timestamp that will be used as reference for any mocked `Date` objects.

    import assert from 'node:assert';
    import { test } from 'node:test';

    test('runAll functions following the given order', (context) => {
      const now = Date.now();
      const setTime = 1000;
      // Date.now is not mocked
      assert.deepStrictEqual(Date.now(), now);

      context.mock.timers.enable({ apis: ['Date'] });
      context.mock.timers.setTime(setTime);
      // Date.now is now 1000
      assert.strictEqual(Date.now(), setTime);
    });
    const assert = require('node:assert');
    const { test } = require('node:test');

    test('setTime replaces current time', (context) => {
      const now = Date.now();
      const setTime = 1000;
      // Date.now is not mocked
      assert.deepStrictEqual(Date.now(), now);

      context.mock.timers.enable({ apis: ['Date'] });
      context.mock.timers.setTime(setTime);
      // Date.now is now 1000
      assert.strictEqual(Date.now(), setTime);
    });
    javascript

##### Dates and Timers working together#

Dates and timer objects are dependent on each other. If you use `setTime()` to pass the current time to the mocked `Date` object, the set timers with `setTimeout` and `setInterval` will not be affected.

However, the `tick` method will advance the mocked `Date` object.

    import assert from 'node:assert';
    import { test } from 'node:test';

    test('runAll functions following the given order', (context) => {
      context.mock.timers.enable({ apis: ['setTimeout', 'Date'] });
      const results = [];
      setTimeout(() => results.push(1), 9999);

      assert.deepStrictEqual(results, []);
      context.mock.timers.setTime(12000);
      assert.deepStrictEqual(results, []);
      // The date is advanced but the timers don't tick
      assert.strictEqual(Date.now(), 12000);
    });
    const assert = require('node:assert');
    const { test } = require('node:test');

    test('runAll functions following the given order', (context) => {
      context.mock.timers.enable({ apis: ['setTimeout', 'Date'] });
      const results = [];
      setTimeout(() => results.push(1), 9999);

      assert.deepStrictEqual(results, []);
      context.mock.timers.setTime(12000);
      assert.deepStrictEqual(results, []);
      // The date is advanced but the timers don't tick
      assert.strictEqual(Date.now(), 12000);
    });
    javascript

### Class: `TestsStream`#

Added in: v18.9.0, v16.19.0
History

Version | Changes
--- | ---
v26.3.0 | Added `parentId` to test events that carry a `testId`.
v20.0.0, v19.9.0, v18.17.0 | added type to test:pass and test:fail events for when the test is a suite.

- Extends `<Readable>`

A successful call to `run()` method will return a new `<TestsStream>` object, streaming a series of events representing the execution of the tests. `TestsStream` will emit events, in the order of the tests definition

Some of the events are guaranteed to be emitted in the same order as the tests are defined, while others are emitted in the order that the tests execute.

#### Event: `'test:coverage'`#

- `data` `<Object>`
  - `summary` `<Object>` An object containing the coverage report.
    - `files` `<Array>` An array of coverage reports for individual files. Each report is an object with the following schema:
      - `path` `<string>` The absolute path of the file.
      - `totalLineCount` `<number>` The total number of lines.
      - `totalBranchCount` `<number>` The total number of branches.
      - `totalFunctionCount` `<number>` The total number of functions.
      - `coveredLineCount` `<number>` The number of covered lines.
      - `coveredBranchCount` `<number>` The number of covered branches.
      - `coveredFunctionCount` `<number>` The number of covered functions.
      - `coveredLinePercent` `<number>` The percentage of lines covered.
      - `coveredBranchPercent` `<number>` The percentage of branches covered.
      - `coveredFunctionPercent` `<number>` The percentage of functions covered.
      - `functions` `<Array>` An array of functions representing function coverage.
        - `name` `<string>` The name of the function.
        - `line` `<number>` The line number where the function is defined.
        - `count` `<number>` The number of times the function was called.
      - `branches` `<Array>` An array of branches representing branch coverage.
        - `line` `<number>` The line number where the branch is defined.
        - `count` `<number>` The number of times the branch was taken.
      - `lines` `<Array>` An array of lines representing line numbers and the number of times they were covered.
        - `line` `<number>` The line number.
        - `count` `<number>` The number of times the line was covered.
    - `thresholds` `<Object>` An object containing whether or not the coverage for each coverage type.
      - `function` `<number>` The function coverage threshold.
      - `branch` `<number>` The branch coverage threshold.
      - `line` `<number>` The line coverage threshold.
    - `totals` `<Object>` An object containing a summary of coverage for all files.
      - `totalLineCount` `<number>` The total number of lines.
      - `totalBranchCount` `<number>` The total number of branches.
      - `totalFunctionCount` `<number>` The total number of functions.
      - `coveredLineCount` `<number>` The number of covered lines.
      - `coveredBranchCount` `<number>` The number of covered branches.
      - `coveredFunctionCount` `<number>` The number of covered functions.
      - `coveredLinePercent` `<number>` The percentage of lines covered.
      - `coveredBranchPercent` `<number>` The percentage of branches covered.
      - `coveredFunctionPercent` `<number>` The percentage of functions covered.
    - `workingDirectory` `<string>` The working directory when code coverage began. This is useful for displaying relative path names in case the tests changed the working directory of the Node.js process.
  - `nesting` `<number>` The nesting level of the test.

Emitted when code coverage is enabled and all tests have completed.

#### Event: `'test:complete'`#

- `data` `<Object>`
  - `column` `<number>` | `<undefined>` The column number where the test is defined, or `undefined` if the test was run through the REPL.
  - `details` `<Object>` Additional execution metadata.
    - `passed` `<boolean>` Whether the test passed or not.
    - `duration_ms` `<number>` The duration of the test in milliseconds.
    - `error` `<Error>` | `<undefined>` An error wrapping the error thrown by the test if it did not pass.
      - `cause` `<Error>` The actual error thrown by the test.
    - `type` `<string>` | `<undefined>` The type of the test, used to denote whether this is a suite.
  - `file` `<string>` | `<undefined>` The path of the test file, `undefined` if test was run through the REPL.
  - `line` `<number>` | `<undefined>` The line number where the test is defined, or `undefined` if the test was run through the REPL.
  - `name` `<string>` The test name.
  - `nesting` `<number>` The nesting level of the test.
  - `parentId` `<number>` | `<undefined>` The `testId` of the enclosing test, or `undefined` for top-level tests. Lets custom reporters track lineage when concurrent siblings at the same nesting level interleave.
  - `tags` `<string>`[] The flattened lowercased tags declared on the test and its ancestor suites, in declaration order. Empty for untagged tests. See Test tags.
  - `testId` `<number>` A numeric identifier for this test instance, unique within the test file's process. Consistent across all events for the same test instance, enabling reliable correlation in custom reporters.
  - `testNumber` `<number>` The ordinal number of the test.
  - `todo` `<string>` | `<boolean>` | `<undefined>` Present if `context.todo` is called
  - `skip` `<string>` | `<boolean>` | `<undefined>` Present if `context.skip` is called

Emitted when a test completes its execution. This event is not emitted in the same order as the tests are defined. The corresponding declaration ordered events are `'test:pass'` and `'test:fail'`.

#### Event: `'test:dequeue'`#

- `data` `<Object>`
  - `column` `<number>` | `<undefined>` The column number where the test is defined, or `undefined` if the test was run through the REPL.
  - `file` `<string>` | `<undefined>` The path of the test file, `undefined` if test was run through the REPL.
  - `line` `<number>` | `<undefined>` The line number where the test is defined, or `undefined` if the test was run through the REPL.
  - `name` `<string>` The test name.
  - `nesting` `<number>` The nesting level of the test.
  - `parentId` `<number>` | `<undefined>` The `testId` of the enclosing test, or `undefined` for top-level tests. Lets custom reporters track lineage when concurrent siblings at the same nesting level interleave.
  - `tags` `<string>`[] The flattened lowercased tags declared on the test and its ancestor suites, in declaration order. Empty for untagged tests. See Test tags.
  - `testId` `<number>` A numeric identifier for this test instance, unique within the test file's process. Consistent across all events for the same test instance, enabling reliable correlation in custom reporters.
  - `type` `<string>` The test type. Either `'suite'` or `'test'`.

Emitted when a test is dequeued, right before it is executed. This event is not guaranteed to be emitted in the same order as the tests are defined. The corresponding declaration ordered event is `'test:start'`.

#### Event: `'test:diagnostic'`#

- `data` `<Object>`
  - `column` `<number>` | `<undefined>` The column number where the test is defined, or `undefined` if the test was run through the REPL.
  - `file` `<string>` | `<undefined>` The path of the test file, `undefined` if test was run through the REPL.
  - `line` `<number>` | `<undefined>` The line number where the test is defined, or `undefined` if the test was run through the REPL.
  - `message` `<string>` The diagnostic message.
  - `nesting` `<number>` The nesting level of the test.
  - `level` `<string>` The severity level of the diagnostic message. Possible values are:
    - `'info'`: Informational messages.
    - `'warn'`: Warnings.
    - `'error'`: Errors.

Emitted when `context.diagnostic` is called. This event is guaranteed to be emitted in the same order as the tests are defined.

#### Event: `'test:enqueue'`#

- `data` `<Object>`
  - `column` `<number>` | `<undefined>` The column number where the test is defined, or `undefined` if the test was run through the REPL.
  - `file` `<string>` | `<undefined>` The path of the test file, `undefined` if test was run through the REPL.
  - `line` `<number>` | `<undefined>` The line number where the test is defined, or `undefined` if the test was run through the REPL.
  - `name` `<string>` The test name.
  - `nesting` `<number>` The nesting level of the test.
  - `parentId` `<number>` | `<undefined>` The `testId` of the enclosing test, or `undefined` for top-level tests. Lets custom reporters track lineage when concurrent siblings at the same nesting level interleave.
  - `tags` `<string>`[] The flattened lowercased tags declared on the test and its ancestor suites, in declaration order. Empty for untagged tests. See Test tags.
  - `testId` `<number>` A numeric identifier for this test instance, unique within the test file's process. Consistent across all events for the same test instance, enabling reliable correlation in custom reporters.
  - `type` `<string>` The test type. Either `'suite'` or `'test'`.

Emitted when a test is enqueued for execution.

#### Event: `'test:fail'`#

- `data` `<Object>`
  - `column` `<number>` | `<undefined>` The column number where the test is defined, or `undefined` if the test was run through the REPL.
  - `details` `<Object>` Additional execution metadata.
    - `duration_ms` `<number>` The duration of the test in milliseconds.
    - `error` `<Error>` An error wrapping the error thrown by the test.
      - `cause` `<Error>` The actual error thrown by the test.
    - `type` `<string>` | `<undefined>` The type of the test, used to denote whether this is a suite.
    - `attempt` `<number>` | `<undefined>` The attempt number of the test run, present only when using the `--test-rerun-failures` flag.
  - `file` `<string>` | `<undefined>` The path of the test file, `undefined` if test was run through the REPL.
  - `line` `<number>` | `<undefined>` The line number where the test is defined, or `undefined` if the test was run through the REPL.
  - `name` `<string>` The test name.
  - `nesting` `<number>` The nesting level of the test.
  - `parentId` `<number>` | `<undefined>` The `testId` of the enclosing test, or `undefined` for top-level tests. Lets custom reporters track lineage when concurrent siblings at the same nesting level interleave.
  - `tags` `<string>`[] The flattened lowercased tags declared on the test and its ancestor suites, in declaration order. Empty for untagged tests. See Test tags.
  - `testId` `<number>` A numeric identifier for this test instance, unique within the test file's process. Consistent across all events for the same test instance, enabling reliable correlation in custom reporters.
  - `testNumber` `<number>` The ordinal number of the test.
  - `todo` `<string>` | `<boolean>` | `<undefined>` Present if `context.todo` is called
  - `skip` `<string>` | `<boolean>` | `<undefined>` Present if `context.skip` is called

Emitted when a test fails. This event is guaranteed to be emitted in the same order as the tests are defined. The corresponding execution ordered event is `'test:complete'`.

#### Event: `'test:interrupted'`#

Added in: v25.7.0

- `data` `<Object>`
  - `tests` `<Array>` An array of objects containing information about the interrupted tests.
    - `column` `<number>` | `<undefined>` The column number where the test is defined, or `undefined` if the test was run through the REPL.
    - `file` `<string>` | `<undefined>` The path of the test file, `undefined` if test was run through the REPL.
    - `line` `<number>` | `<undefined>` The line number where the test is defined, or `undefined` if the test was run through the REPL.
    - `name` `<string>` The test name.
    - `nesting` `<number>` The nesting level of the test.

Emitted when the test runner is interrupted by a `SIGINT` signal (e.g., when pressing `Ctrl`+`C`). The event contains information about the tests that were running at the time of interruption.

When using process isolation (the default), the test name will be the file path since the parent runner only knows about file-level tests. When using `--test-isolation=none`, the actual test name is shown.

#### Event: `'test:pass'`#

- `data` `<Object>`
  - `column` `<number>` | `<undefined>` The column number where the test is defined, or `undefined` if the test was run through the REPL.
  - `details` `<Object>` Additional execution metadata.
    - `duration_ms` `<number>` The duration of the test in milliseconds.
    - `type` `<string>` | `<undefined>` The type of the test, used to denote whether this is a suite.
    - `attempt` `<number>` | `<undefined>` The attempt number of the test run, present only when using the `--test-rerun-failures` flag.
    - `passed_on_attempt` `<number>` | `<undefined>` The attempt number the test passed on, present only when using the `--test-rerun-failures` flag.
  - `file` `<string>` | `<undefined>` The path of the test file, `undefined` if test was run through the REPL.
  - `line` `<number>` | `<undefined>` The line number where the test is defined, or `undefined` if the test was run through the REPL.
  - `name` `<string>` The test name.
  - `nesting` `<number>` The nesting level of the test.
  - `parentId` `<number>` | `<undefined>` The `testId` of the enclosing test, or `undefined` for top-level tests. Lets custom reporters track lineage when concurrent siblings at the same nesting level interleave.
  - `tags` `<string>`[] The flattened lowercased tags declared on the test and its ancestor suites, in declaration order. Empty for untagged tests. See Test tags.
  - `testId` `<number>` A numeric identifier for this test instance, unique within the test file's process. Consistent across all events for the same test instance, enabling reliable correlation in custom reporters.
  - `testNumber` `<number>` The ordinal number of the test.
  - `todo` `<string>` | `<boolean>` | `<undefined>` Present if `context.todo` is called
  - `skip` `<string>` | `<boolean>` | `<undefined>` Present if `context.skip` is called

Emitted when a test passes. This event is guaranteed to be emitted in the same order as the tests are defined. The corresponding execution ordered event is `'test:complete'`.

#### Event: `'test:plan'`#

- `data` `<Object>`
  - `column` `<number>` | `<undefined>` The column number where the test is defined, or `undefined` if the test was run through the REPL.
  - `file` `<string>` | `<undefined>` The path of the test file, `undefined` if test was run through the REPL.
  - `line` `<number>` | `<undefined>` The line number where the test is defined, or `undefined` if the test was run through the REPL.
  - `nesting` `<number>` The nesting level of the test.
  - `count` `<number>` The number of subtests that have ran.

Emitted when all subtests have completed for a given test. This event is guaranteed to be emitted in the same order as the tests are defined.

#### Event: `'test:start'`#

- `data` `<Object>`
  - `column` `<number>` | `<undefined>` The column number where the test is defined, or `undefined` if the test was run through the REPL.
  - `file` `<string>` | `<undefined>` The path of the test file, `undefined` if test was run through the REPL.
  - `line` `<number>` | `<undefined>` The line number where the test is defined, or `undefined` if the test was run through the REPL.
  - `name` `<string>` The test name.
  - `nesting` `<number>` The nesting level of the test.
  - `parentId` `<number>` | `<undefined>` The `testId` of the enclosing test, or `undefined` for top-level tests. Lets custom reporters track lineage when concurrent siblings at the same nesting level interleave.
  - `tags` `<string>`[] The flattened lowercased tags declared on the test and its ancestor suites, in declaration order. Empty for untagged tests. See Test tags.
  - `testId` `<number>` A numeric identifier for this test instance, unique within the test file's process. Consistent across all events for the same test instance, enabling reliable correlation in custom reporters.

Emitted when a test starts reporting its own and its subtests status. This event is guaranteed to be emitted in the same order as the tests are defined. The corresponding execution ordered event is `'test:dequeue'`.

#### Event: `'test:stderr'`#

- `data` `<Object>`
  - `file` `<string>` The path of the test file.
  - `message` `<string>` The message written to `stderr`.

Emitted when a running test writes to `stderr`. This event is only emitted if `--test` flag is passed. This event is not guaranteed to be emitted in the same order as the tests are defined.

#### Event: `'test:stdout'`#

- `data` `<Object>`
  - `file` `<string>` The path of the test file.
  - `message` `<string>` The message written to `stdout`.

Emitted when a running test writes to `stdout`. This event is only emitted if `--test` flag is passed. This event is not guaranteed to be emitted in the same order as the tests are defined.

#### Event: `'test:summary'`#

- `data` `<Object>`
  - `counts` `<Object>` An object containing the counts of various test results.
    - `cancelled` `<number>` The total number of cancelled tests.
    - `failed` `<number>` The total number of failed tests.
    - `passed` `<number>` The total number of passed tests.
    - `skipped` `<number>` The total number of skipped tests.
    - `suites` `<number>` The total number of suites run.
    - `tests` `<number>` The total number of tests run, excluding suites.
    - `todo` `<number>` The total number of TODO tests.
    - `topLevel` `<number>` The total number of top level tests and suites.
  - `duration_ms` `<number>` The duration of the test run in milliseconds.
  - `file` `<string>` | `<undefined>` The path of the test file that generated the summary. If the summary corresponds to multiple files, this value is `undefined`.
  - `success` `<boolean>` Indicates whether or not the test run is considered successful or not. If any error condition occurs, such as a failing test or unmet coverage threshold, this value will be set to `false`.

Emitted when a test run completes. This event contains metrics pertaining to the completed test run, and is useful for determining if a test run passed or failed. If process-level test isolation is used, a `'test:summary'` event is generated for each test file in addition to a final cumulative summary.

#### Event: `'test:watch:drained'`#

Emitted when no more tests are queued for execution in watch mode.

#### Event: `'test:watch:restarted'`#

Emitted when one or more tests are restarted due to a file change in watch mode.

### `getTestContext()`#

Added in: v26.1.0

- Returns: `<TestContext>` | `<SuiteContext>` | `<undefined>`

Returns the `TestContext` or `SuiteContext` object associated with the currently executing test or suite, or `undefined` if called outside of a test or suite. This function can be used to access context information from within the test or suite function or any async operations within them.

    import { getTestContext } from 'node:test';

    test('example test', async () => {
      const ctx = getTestContext();
      console.log(`Running test: ${ctx.name}`);
    });

    describe('example suite', () => {
      const ctx = getTestContext();
      console.log(`Running suite: ${ctx.name}`);
    });
    mjs

When called from a test, returns a `TestContext`. When called from a suite, returns a `SuiteContext`.

If called from outside a test or suite (e.g., at the top level of a module or in a setTimeout callback after execution has completed), this function returns `undefined`.

When called from within a hook (before, beforeEach, after, afterEach), this function returns the context of the test or suite that the hook is associated with.

### Test instrumentation and OpenTelemetry#

Added in: v26.1.0

The test runner publishes test execution events through the Node.js `diagnostics_channel` module, enabling integration with observability tools like OpenTelemetry without requiring changes to the test runner itself.

#### Tracing events#

The test runner publishes events to the `'node.test'` tracing channel. Subscribers can use the `TracingChannel` API to bind context or perform custom instrumentation.

##### Channel: `'tracing:node.test:start'`#

- `data` `<Object>`
  - `name` `<string>` The name of the test.
  - `nesting` `<number>` The nesting level of the test.
  - `file` `<string>` | `<undefined>` The path to the test file, or `undefined` when running in the REPL.
  - `type` `<string>` The type of test. Either `'test'` or `'suite'`.

Emitted when a test or suite starts execution. The test's span encompasses all of its before, beforeEach, and afterEach hooks, as well as the test body.

##### Channel: `'tracing:node.test:end'`#

- `data` `<Object>`
  - `name` `<string>` The name of the test.
  - `nesting` `<number>` The nesting level of the test.
  - `file` `<string>` | `<undefined>` The path to the test file, or `undefined` when running in the REPL.
  - `type` `<string>` The type of test. Either `'test'` or `'suite'`.

Emitted when a test or suite finishes execution.

##### Channel: `'tracing:node.test:error'`#

- `data` `<Object>`
  - `name` `<string>` The name of the test.
  - `nesting` `<number>` The nesting level of the test.
  - `file` `<string>` | `<undefined>` The path to the test file, or `undefined` when running in the REPL.
  - `type` `<string>` The type of test. Either `'test'` or `'suite'`.
  - `error` `<Error>` The error that was thrown.

Emitted when a test or suite throws an error.

#### Context propagation with `bindStore()`#

The tracing channel can be used to propagate context through test execution by binding an `AsyncLocalStorage` instance. This allows context to be automatically available in the test function and all async operations within the test.

    import dc from 'node:diagnostics_channel';
    import { AsyncLocalStorage } from 'node:async_hooks';

    const testStorage = new AsyncLocalStorage();
    const testChannel = dc.tracingChannel('node.test');

    // Bind context to test execution — the returned value becomes the store
    testChannel.start.bindStore(testStorage, (data) => {
      return { testName: data.name, startTime: Date.now() };
    });

    // Optionally handle errors and cleanup
    testChannel.error.subscribe((data) => {
      const store = testStorage.getStore();
      console.log(`Test "${data.name}" failed after ${Date.now() - store.startTime}ms`);
    });

    testChannel.end.subscribe((data) => {
      const store = testStorage.getStore();
      console.log(`Test "${data.name}" completed in ${Date.now() - store.startTime}ms`);
    });
    mjs

When using `bindStore()`, the context provided will be automatically propagated to the test function and all async operations within the test, without requiring any additional instrumentation in the test code.

### Class: `TestContext`#

Added in: v18.0.0, v16.17.0
History

Version | Changes
--- | ---
v20.1.0, v18.17.0 | The `before` function was added to TestContext.

An instance of `TestContext` is passed to each test function in order to interact with the test runner. However, the `TestContext` constructor is not exposed as part of the API.

#### `context.before([fn][, options])`#

Added in: v20.1.0, v18.17.0

- `fn` `<Function>` | `<AsyncFunction>` The hook function. The first argument to this function is a `TestContext` object. If the hook uses callbacks, the callback function is passed as the second argument. Default: A no-op function.
- `options` `<Object>` Configuration options for the hook. The following properties are supported:
  - `signal` `<AbortSignal>` Allows aborting an in-progress hook.
  - `timeout` `<number>` A number of milliseconds the hook will fail after. If unspecified, subtests inherit this value from their parent. Default: `Infinity`.

This function is used to create a hook running before subtest of the current test.

#### `context.beforeEach([fn][, options])`#

Added in: v18.8.0, v16.18.0

- `fn` `<Function>` | `<AsyncFunction>` The hook function. The first argument to this function is a `TestContext` object. If the hook uses callbacks, the callback function is passed as the second argument. Default: A no-op function.
- `options` `<Object>` Configuration options for the hook. The following properties are supported:
  - `signal` `<AbortSignal>` Allows aborting an in-progress hook.
  - `timeout` `<number>` A number of milliseconds the hook will fail after. If unspecified, subtests inherit this value from their parent. Default: `Infinity`.

This function is used to create a hook running before each subtest of the current test.

    test('top level test', async (t) => {
      t.beforeEach((t) => t.diagnostic(`about to run ${t.name}`));
      await t.test(
        'This is a subtest',
        (t) => {
          // Some relevant assertion here
        },
      );
    });
    js

#### `context.after([fn][, options])`#

Added in: v19.3.0, v18.13.0

- `fn` `<Function>` | `<AsyncFunction>` The hook function. The first argument to this function is a `TestContext` object. If the hook uses callbacks, the callback function is passed as the second argument. Default: A no-op function.
- `options` `<Object>` Configuration options for the hook. The following properties are supported:
  - `signal` `<AbortSignal>` Allows aborting an in-progress hook.
  - `timeout` `<number>` A number of milliseconds the hook will fail after. If unspecified, subtests inherit this value from their parent. Default: `Infinity`.

This function is used to create a hook that runs after the current test finishes.

    test('top level test', async (t) => {
      t.after((t) => t.diagnostic(`finished running ${t.name}`));
      // Some relevant assertion here
    });
    js

#### `context.afterEach([fn][, options])`#

Added in: v18.8.0, v16.18.0

- `fn` `<Function>` | `<AsyncFunction>` The hook function. The first argument to this function is a `TestContext` object. If the hook uses callbacks, the callback function is passed as the second argument. Default: A no-op function.
- `options` `<Object>` Configuration options for the hook. The following properties are supported:
  - `signal` `<AbortSignal>` Allows aborting an in-progress hook.
  - `timeout` `<number>` A number of milliseconds the hook will fail after. If unspecified, subtests inherit this value from their parent. Default: `Infinity`.

This function is used to create a hook running after each subtest of the current test.

    test('top level test', async (t) => {
      t.afterEach((t) => t.diagnostic(`finished running ${t.name}`));
      await t.test(
        'This is a subtest',
        (t) => {
          // Some relevant assertion here
        },
      );
    });
    js

#### `context.assert`#

Added in: v22.2.0, v20.15.0

An object containing assertion methods bound to `context`. The top-level functions from the `node:assert` module are exposed here for the purpose of creating test plans.

    test('test', (t) => {
      t.plan(1);
      t.assert.strictEqual(true, true);
    });
    js

##### `context.assert.fileSnapshot(value, path[, options])`#

Added in: v23.7.0, v22.14.0

- `value` `<any>` A value to serialize to a string. If Node.js was started with the `--test-update-snapshots` flag, the serialized value is written to `path`. Otherwise, the serialized value is compared to the contents of the existing snapshot file.
- `path` `<string>` The file where the serialized `value` is written.
- `options` `<Object>` Optional configuration options. The following properties are supported:
  - `serializers` `<Array>` An array of synchronous functions used to serialize `value` into a string. `value` is passed as the only argument to the first serializer function. The return value of each serializer is passed as input to the next serializer. Once all serializers have run, the resulting value is coerced to a string. Default: If no serializers are provided, the test runner's default serializers are used.

This function serializes `value` and writes it to the file specified by `path`.

    test('snapshot test with default serialization', (t) => {
      t.assert.fileSnapshot({ value1: 1, value2: 2 }, './snapshots/snapshot.json');
    });
    js

This function differs from `context.assert.snapshot()` in the following ways:

- The snapshot file path is explicitly provided by the user.
- Each snapshot file is limited to a single snapshot value.
- No additional escaping is performed by the test runner.

These differences allow snapshot files to better support features such as syntax highlighting.

##### `context.assert.snapshot(value[, options])`#

Added in: v22.3.0

- `value` `<any>` A value to serialize to a string. If Node.js was started with the `--test-update-snapshots` flag, the serialized value is written to the snapshot file. Otherwise, the serialized value is compared to the corresponding value in the existing snapshot file.
- `options` `<Object>` Optional configuration options. The following properties are supported:
  - `serializers` `<Array>` An array of synchronous functions used to serialize `value` into a string. `value` is passed as the only argument to the first serializer function. The return value of each serializer is passed as input to the next serializer. Once all serializers have run, the resulting value is coerced to a string. Default: If no serializers are provided, the test runner's default serializers are used.

This function implements assertions for snapshot testing.

    test('snapshot test with default serialization', (t) => {
      t.assert.snapshot({ value1: 1, value2: 2 });
    });

    test('snapshot test with custom serialization', (t) => {
      t.assert.snapshot({ value3: 3, value4: 4 }, {
        serializers: [(value) => JSON.stringify(value)],
      });
    });
    js

#### `context.diagnostic(message)`#

Added in: v18.0.0, v16.17.0

- `message` `<string>` Message to be reported.

This function is used to write diagnostics to the output. Any diagnostic information is included at the end of the test's results. This function does not return a value.

    test('top level test', (t) => {
      t.diagnostic('A diagnostic message');
    });
    js

#### `context.filePath`#

Added in: v22.6.0, v20.16.0

The absolute path of the test file that created the current test. If a test file imports additional modules that generate tests, the imported tests will return the path of the root test file.

#### `context.fullName`#

Added in: v22.3.0, v20.16.0

The name of the test and each of its ancestors, separated by `>`.

#### `context.name`#

Added in: v18.8.0, v16.18.0

The name of the test.

#### `context.passed`#

Added in: v21.7.0, v20.12.0

- Type: `<boolean>` `false` before the test is executed, e.g. in a `beforeEach` hook.

Indicated whether the test succeeded.

#### `context.error`#

Added in: v21.7.0, v20.12.0

- Type: `<Error>` | `<null>`

The failure reason for the test/case; wrapped and available via `context.error.cause`.

#### `context.attempt`#

Added in: v25.0.0

- Type: `<number>`

The attempt number of the test. This value is zero-based, so the first attempt is `0`, the second attempt is `1`, and so on. This property is useful in conjunction with the `--test-rerun-failures` option to determine which attempt the test is currently running.

#### `context.tags`#

Added in: v26.2.0

Stability: 1.0 - Early development

- Type: `<string>`[]

A frozen array of the test's flattened lowercased tags, in declaration order, including any tags inherited from ancestor suites. Empty when the test has no tags. See Test tags.

#### `context.workerId`#

Added in: v25.8.0

- Type: `<number>` | `<undefined>`

The unique identifier of the worker running the current test file. This value is derived from the `NODE_TEST_WORKER_ID` environment variable. When running tests with `--test-isolation=process` (the default), each test file runs in a separate child process and is assigned a worker ID from 1 to N, where N is the number of concurrent workers. When running with `--test-isolation=none`, all tests run in the same process and the worker ID is always 1. This value is `undefined` when not running in a test context.

This property is useful for splitting resources (like database connections or server ports) across concurrent test files:

    import { test } from 'node:test';
    import { process } from 'node:process';

    test('database operations', async (t) => {
      // Worker ID is available via context
      console.log(`Running in worker ${t.workerId}`);

      // Or via environment variable (available at import time)
      const workerId = process.env.NODE_TEST_WORKER_ID;
      // Use workerId to allocate separate resources per worker
    });
    mjs

#### `context.plan(count[,options])`#

Added in: v22.2.0, v20.15.0
History

Version | Changes
--- | ---
v23.9.0, v22.15.0 | Add the `options` parameter.
v23.4.0, v22.13.0 | This function is no longer experimental.

- `count` `<number>` The number of assertions and subtests that are expected to run.
- `options` `<Object>` Additional options for the plan.
  - `wait` `<boolean>` | `<number>` The wait time for the plan:
    - If `true`, the plan waits indefinitely for all assertions and subtests to run.
    - If `false`, the plan performs an immediate check after the test function completes, without waiting for any pending assertions or subtests. Any assertions or subtests that complete after this check will not be counted towards the plan.
    - If a number, it specifies the maximum wait time in milliseconds before timing out while waiting for expected assertions and subtests to be matched. If the timeout is reached, the test will fail. Default: `false`.

This function is used to set the number of assertions and subtests that are expected to run within the test. If the number of assertions and subtests that run does not match the expected count, the test will fail.

> Note: To make sure assertions are tracked, `t.assert` must be used instead of `assert` directly.

    test('top level test', (t) => {
      t.plan(2);
      t.assert.ok('some relevant assertion here');
      t.test('subtest', () => {});
    });
    js

When working with asynchronous code, the `plan` function can be used to ensure that the correct number of assertions are run:

    test('planning with streams', (t, done) => {
      function* generate() {
        yield 'a';
        yield 'b';
        yield 'c';
      }
      const expected = ['a', 'b', 'c'];
      t.plan(expected.length);
      const stream = Readable.from(generate());
      stream.on('data', (chunk) => {
        t.assert.strictEqual(chunk, expected.shift());
      });

      stream.on('end', () => {
        done();
      });
    });
    js

When using the `wait` option, you can control how long the test will wait for the expected assertions. For example, setting a maximum wait time ensures that the test will wait for asynchronous assertions to complete within the specified timeframe:

    test('plan with wait: 2000 waits for async assertions', (t) => {
      t.plan(1, { wait: 2000 }); // Waits for up to 2 seconds for the assertion to complete.

      const asyncActivity = () => {
        setTimeout(() => {
          t.assert.ok(true, 'Async assertion completed within the wait time');
        }, 1000); // Completes after 1 second, within the 2-second wait time.
      };

      asyncActivity(); // The test will pass because the assertion is completed in time.
    });
    js

Note: If a `wait` timeout is specified, it begins counting down only after the test function finishes executing.

#### `context.runOnly(shouldRunOnlyTests)`#

Added in: v18.0.0, v16.17.0

- `shouldRunOnlyTests` `<boolean>` Whether or not to run `only` tests.

If `shouldRunOnlyTests` is truthy, the test context will only run tests that have the `only` option set. Otherwise, all tests are run. If Node.js was not started with the `--test-only` command-line option, this function is a no-op.

    test('top level test', (t) => {
      // The test context can be set to run subtests with the 'only' option.
      t.runOnly(true);
      return Promise.all([
        t.test('this subtest is now skipped'),
        t.test('this subtest is run', { only: true }),
      ]);
    });
    js

#### `context.signal`#

Added in: v18.7.0, v16.17.0

- Type: `<AbortSignal>`

Can be used to abort test subtasks when the test has been aborted.

    test('top level test', async (t) => {
      await fetch('some/uri', { signal: t.signal });
    });
    js

#### `context.skip([message])`#

Added in: v18.0.0, v16.17.0

- `message` `<string>` Optional skip message.

This function causes the test's output to indicate the test as skipped. If `message` is provided, it is included in the output. Calling `skip()` does not terminate execution of the test function. This function does not return a value.

    test('top level test', (t) => {
      // Make sure to return here as well if the test contains additional logic.
      t.skip('this is skipped');
    });
    js

#### `context.todo([message])`#

Added in: v18.0.0, v16.17.0

- `message` `<string>` Optional `TODO` message.

This function adds a `TODO` directive to the test's output. If `message` is provided, it is included in the output. Calling `todo()` does not terminate execution of the test function. This function does not return a value.

    test('top level test', (t) => {
      // This test is marked as `TODO`
      t.todo('this is a todo');
    });
    js

#### `context.test([name][, options][, fn])`#

Added in: v18.0.0, v16.17.0
History

Version | Changes
--- | ---
v26.2.0 | Added the `tags` option.
v18.8.0, v16.18.0 | Add a `signal` option.
v18.7.0, v16.17.0 | Add a `timeout` option.

- `name` `<string>` The name of the subtest, which is displayed when reporting test results. Default: The `name` property of `fn`, or `'<anonymous>'` if `fn` does not have a name.
- `options` `<Object>` Configuration options for the subtest. The following properties are supported:
  - `concurrency` `<number>` | `<boolean>` | `<null>` If a number is provided, then that many tests would run asynchronously (they are still managed by the single-threaded event loop). If `true`, it would run all subtests in parallel. If `false`, it would only run one test at a time. If unspecified, subtests inherit this value from their parent. Default: `null`.
  - `only` `<boolean>` If truthy, and the test context is configured to run `only` tests, then this test will be run. Otherwise, the test is skipped. Default: `false`.
  - `signal` `<AbortSignal>` Allows aborting an in-progress test.
  - `skip` `<boolean>` | `<string>` If truthy, the test is skipped. If a string is provided, that string is displayed in the test results as the reason for skipping the test. Default: `false`.
  - `tags` `<string>`[] An array of string labels associated with the subtest. Used together with `--experimental-test-tag-filter` to filter which tests run. Tags inherit from the parent test or suite by union. See Test tags. Default: `[]`.
  - `todo` `<boolean>` | `<string>` If truthy, the test marked as `TODO`. If a string is provided, that string is displayed in the test results as the reason why the test is `TODO`. Default: `false`.
  - `timeout` `<number>` A number of milliseconds the test will fail after. If unspecified, subtests inherit this value from their parent. Default: `Infinity`.
  - `plan` `<number>` The number of assertions and subtests expected to be run in the test. If the number of assertions run in the test does not match the number specified in the plan, the test will fail. Default: `undefined`.
- `fn` `<Function>` | `<AsyncFunction>` The function under test. The first argument to this function is a `TestContext` object. If the test uses callbacks, the callback function is passed as the second argument. Default: A no-op function.
- Returns: `<Promise>` Fulfilled with `undefined` once the test completes.

This function is used to create subtests under the current test. This function behaves in the same fashion as the top level `test()` function.

    test('top level test', async (t) => {
      await t.test(
        'This is a subtest',
        { only: false, skip: false, concurrency: 1, todo: false, plan: 1 },
        (t) => {
          t.assert.ok('some relevant assertion here');
        },
      );
    });
    js

#### `context.waitFor(condition[, options])`#

Added in: v23.7.0, v22.14.0

- `condition` `<Function>` | `<AsyncFunction>` An assertion function that is invoked periodically until it completes successfully or the defined polling timeout elapses. Successful completion is defined as not throwing or rejecting. This function does not accept any arguments, and is allowed to return any value.
- `options` `<Object>` An optional configuration object for the polling operation. The following properties are supported:
  - `interval` `<number>` The number of milliseconds to wait after an unsuccessful invocation of `condition` before trying again. Default: `50`.
  - `timeout` `<number>` The poll timeout in milliseconds. If `condition` has not succeeded by the time this elapses, an error occurs. Default: `1000`.
- Returns: `<Promise>` Fulfilled with the value returned by `condition`.

This method polls a `condition` function until that function either returns successfully or the operation times out.

### Class: `SuiteContext`#

Added in: v18.7.0, v16.17.0

An instance of `SuiteContext` is passed to each suite function in order to interact with the test runner. However, the `SuiteContext` constructor is not exposed as part of the API.

#### `context.filePath`#

Added in: v22.6.0

The absolute path of the test file that created the current suite. If a test file imports additional modules that generate suites, the imported suites will return the path of the root test file.

#### `context.fullName`#

Added in: v22.3.0, v20.16.0

The name of the suite and each of its ancestors, separated by `>`.

#### `context.name`#

Added in: v18.8.0, v16.18.0

The name of the suite.

#### `context.signal`#

Added in: v18.7.0, v16.17.0

- Type: `<AbortSignal>`

Can be used to abort test subtasks when the test has been aborted.

#### `context.passed`#

Added in: v26.1.0

- Type: `<boolean>`

Indicates whether the suite and all of its subtests have passed.

#### `context.attempt`#

Added in: v26.1.0

- Type: `<number>`

The attempt number of the suite. This value is zero-based, so the first attempt is `0`, the second attempt is `1`, and so on. This property is useful in conjunction with the `--test-rerun-failures` option to determine the attempt number of the current run.

#### `context.diagnostic(message)`#

Added in: v26.1.0

- `message` `<string>` A diagnostic message to output.

Output a diagnostic message. This is typically used for logging information about the current suite or its tests.

    test.describe('my suite', (suite) => {
      suite.diagnostic('Suite diagnostic message');
    });
    js