node/test
Aras Abbasi 4f84a3d200
errors: improve formatList in errors.js
PR-URL: https://github.com/nodejs/node/pull/49642
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: LiviaMedeiros <livia@cirno.name>
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
2023-09-29 11:04:38 +00:00
..
abort
addons
async-hooks
benchmark
cctest
common esm: --experimental-default-type flag to flip module defaults 2023-09-29 06:18:44 +00:00
doctool
embedding test: fix argument computation in embedtest 2023-09-18 00:06:20 +02:00
es-module esm: fix cache collision on JSON files using file: URL 2023-09-29 08:46:32 +00:00
fixtures crypto: return clear errors when loading invalid PFX data 2023-09-29 10:56:33 +00:00
fuzzers
internet
js-native-api node-api: enable uncaught exceptions policy by default 2023-09-25 04:23:58 +00:00
known_issues
message errors: improve performance of instantiation 2023-09-28 09:57:38 +00:00
node-api node-api: enable uncaught exceptions policy by default 2023-09-25 04:23:58 +00:00
overlapped-checker
parallel errors: improve formatList in errors.js 2023-09-29 11:04:38 +00:00
pseudo-tty
pummel
report
sequential Revert "test: mark test-http-regr-gh-2928 as flaky" 2023-09-20 18:31:47 +00:00
testpy
tick-processor
tools
v8-updates
wasi
wpt lib: allow byob reader for 'blob.stream()' 2023-09-22 06:16:46 +00: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.