node/test
Filip Skokan e623e1a419
test: fix WPT state when process exits but workers are still running
PR-URL: https://github.com/nodejs/node/pull/47826
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
2023-05-03 08:58:26 +00:00
..
abort
addons
async-hooks tools: fix jsdoc lint 2023-05-02 00:48:20 +00:00
benchmark url: drop ICU requirement for parsing hostnames 2023-04-05 09:05:29 -07:00
cctest quic: add additional quic implementation utilities 2023-03-31 09:58:37 -07:00
common test: fix WPT state when process exits but workers are still running 2023-05-03 08:58:26 +00:00
doctool test: run doctool tests in parallel 2023-04-04 21:02:47 +02:00
embedding src: fix some recently introduced coverity issues 2023-03-28 09:07:55 -04:00
es-module loader: use default loader as cascaded loader in the in loader worker 2023-04-21 12:27:54 +00:00
fixtures v8: fix ERR_NOT_BUILDING_SNAPSHOT is not a constructor 2023-04-29 16:50:42 +00:00
fuzzers
internet dns: expose getDefaultResultOrder 2023-04-26 08:56:04 +00:00
js-native-api node-api: test passing NULL to napi_define_class 2023-04-26 06:38:51 +00:00
known_issues test: remove stale entry from known_issues.status 2023-04-08 16:22:35 +00:00
message test: migrate message tests to use assertSnapshot 2023-04-27 06:41:58 +00:00
node-api node-api: deprecate napi_module_register 2023-03-24 14:00:40 -04:00
overlapped-checker
parallel test: refactor to use getEventListeners in timers 2023-05-03 02:28:57 +00:00
pseudo-tty test_runner: avoid reporting parents of failing tests in summary 2023-04-18 07:36:56 +00:00
pummel test: add and use tmpdir.hasEnoughSpace() 2023-05-01 15:23:49 +00:00
report
sequential quic: add additional QUIC implementation 2023-04-26 13:27:04 +00:00
testpy
tick-processor
tools
v8-updates
wasi wasi: make returnOnExit true by default 2023-04-11 16:35:52 -04:00
wpt test: refactor WPTRunner and enable parallel WPT execution 2023-04-25 11:45:54 +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.