node/test
Bradley Farias 85898e0aca bootstrap: run preload prior to frozen-intrinsics
This is used to allow people to run polyfills.

Co-Authored-By: Anna Henningsen <github@addaleax.net>

PR-URL: https://github.com/nodejs/node/pull/28940
Reviewed-By: Guy Bedford <guybedford@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
2019-08-20 09:49:48 -05:00
..
abort
addons test: make exported method static 2019-08-15 22:58:40 -07:00
async-hooks
benchmark test: add required settings to test-benchmark-buffer 2019-08-16 10:15:38 -07:00
cctest
common test: clean tmpdir on process exit 2019-08-10 19:22:11 -07:00
doctool
es-module esm: support loading data URLs 2019-08-20 09:34:18 -05:00
fixtures bootstrap: run preload prior to frozen-intrinsics 2019-08-20 09:49:48 -05:00
internet
js-native-api test: refactoring test_error testing 2019-08-01 13:12:53 -07:00
known_issues
message test: unskip tests that now pass on AIX 2019-08-10 19:02:57 -07:00
node-api
parallel bootstrap: run preload prior to frozen-intrinsics 2019-08-20 09:49:48 -05:00
pseudo-tty tools: make pty_helper.py python3-compatible 2019-08-19 09:56:35 -07:00
pummel test: clean tmpdir on process exit 2019-08-10 19:22:11 -07:00
report
sequential test: clean tmpdir on process exit 2019-08-10 19:22:11 -07:00
testpy
tick-processor
tools tools: allow single JS file for --link-module 2019-08-12 12:56:43 +02:00
v8-updates test: update postmortem metadata test for V8 7.7 2019-08-19 09:26:21 +02:00
wpt
.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 for when the --abort-on-uncaught-exception flag is used.
addons Yes Tests for addon functionality along with some tests that require an addon.
async-hooks Yes Tests for async_hooks functionality.
benchmark No 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 n-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 n-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.