node/test
2024-02-13 14:55:05 -03:00
..
abort
addons test: fix flakiness in worker*.test-free-called 2024-01-02 15:05:23 -03:00
async-hooks
benchmark benchmark: add undici websocket benchmark 2023-12-15 15:26:22 -03:00
cctest lib,src,permission: port path.resolve to C++ 2024-01-02 15:05:28 -03:00
common net: add connection attempt events 2024-01-02 15:05:24 -03:00
doctool
embedding src: support configurable snapshot 2024-01-02 15:05:22 -03:00
es-module src: do not treat all paths ending with node_modules as such 2024-01-02 15:05:26 -03:00
fixtures lib: use cache fs internals against path traversal 2024-02-13 14:55:05 -03:00
fuzzers
internet net: add connection attempt events 2024-01-02 15:05:24 -03:00
js-native-api node-api: segregate nogc APIs from rest via type system 2024-01-02 15:05:23 -03:00
known_issues
message
node-api node-api: segregate nogc APIs from rest via type system 2024-01-02 15:05:23 -03:00
overlapped-checker
parallel zlib: pause stream if outgoing buffer is full 2024-02-13 15:26:53 +01:00
pseudo-tty
pummel test: fix inconsistency write size in test-fs-readfile-tostring-fail 2024-01-02 15:05:26 -03:00
report
sequential test: fix flaky conditions for ppc64 SEA tests 2024-01-11 10:10:47 -03:00
testpy
tick-processor
tools
v8-updates
wasi
wpt stream: fix code style 2024-01-02 15:05:27 -03:00
.eslintrc.yaml
README.md
root.status

Node.js Core Tests

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 run on Windows, be sure to clone Node.js source code with the autocrlf git config flag set to true.

Test Directories

Directory Runs on CI Purpose
abort Yes Tests that use --abort-on-uncaught-exception and other situations where we want to test something but avoid generating a core file.
addons Yes Tests for addon functionality along with some tests that require an addon.
async-hooks Yes Tests for async_hooks functionality.
benchmark Yes Test minimal functionality of benchmarks.
cctest Yes C++ tests that are run as part of the build process.
code-cache No Tests for a Node.js binary compiled with V8 code cache.
common Common modules shared among many tests. Documentation
doctool Yes Tests for the documentation generator.
es-module Yes Test ESM module loading.
fixtures Test fixtures used in various tests throughout the test suite.
internet No Tests that make real outbound network connections. Tests for networking related modules may also be present in other directories, but those tests do not make outbound connections.
js-native-api Yes Tests for Node.js-agnostic Node-API functionality.
known_issues Yes Tests reproducing known issues within the system. All tests inside of this directory are expected to fail. If a test doesn't fail on certain platforms, those should be skipped via known_issues.status.
message Yes Tests for messages that are output for various conditions (console.log, error messages etc.)
node-api Yes Tests for Node.js-specific Node-API functionality.
parallel Yes Various tests that are able to be run in parallel.
pseudo-tty Yes Tests that require stdin/stdout/stderr to be a TTY.
pummel No Various tests for various modules / system functionality operating under load.
sequential Yes Various tests that must not run in parallel.
testpy Test configuration utility used by various test suites.
tick-processor No Tests for the V8 tick processor integration. The tests are for the logic in lib/internal/v8_prof_processor.js and lib/internal/v8_prof_polyfill.js. The tests confirm that the profile processor packages the correct set of scripts from V8 and introduces the correct platform specific logic.
v8-updates No Tests for V8 performance integration.