This directory contains code and data used to test the Node.js implementation.
For a detailed guide on how to write tests in this directory, see the guide on writing tests.
On how to run tests in this directory, see the contributing guide.
For the tests to successfully run on Windows, Node.js has to be checked out from GitHub with the
autocrlf git config flag set to true.
|Directory||Runs on CI||Purpose|
|Yes||Tests for when the |
|Yes||Tests for addon functionality along with some tests that require an addon to function properly.|
|Yes||Tests for async_hooks functionality.|
|No||Test minimal functionality of benchmarks.|
|Yes||C++ tests that are run as part of the build process.|
|No||Tests for a Node.js binary compiled with V8 code cache.|
|Common modules shared among many tests. Documentation|
|Yes||Tests for the documentation generator.|
|Yes||Test ESM module loading.|
|Test fixtures used in various tests throughout the test suite.|
|No||Tests that make real outbound connections (mainly networking related modules). Tests for networking related modules may also be present in other directories, but those tests do not make outbound connections.|
|Yes||Tests for Node.js-agnostic n-api functionality.|
|Yes||Tests reproducing known issues within the system. All tests inside of this directory are expected to fail consistently. If a test doesn't fail on certain platforms, those should be skipped via |
|Yes||Tests for messages that are output for various conditions (|
|Yes||Tests for Node.js-specific n-api functionality.|
|Yes||Various tests that are able to be run in parallel.|
|Yes||Tests that require stdin/stdout/stderr to be a TTY.|
|No||Various tests for various modules / system functionality operating under load.|
|Yes||Various tests that are run sequentially.|
|Test configuration utility used by various test suites.|
|No||Tests for the V8 tick processor integration. The tests are for the logic in |
|No||Tests for V8 performance integration.|