You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Marja Hölttä 39853683b4 [HACK] test: New test expectation for decoder. 7 years ago
..
abort test,process: run 'abort' suite on Windows 7 years ago
addons test: skip test when checking async_hooks 7 years ago
addons-napi n-api: fix warning about size_t compare with int 7 years ago
async-hooks async_hooks,doc: some async_hooks improvements 7 years ago
cctest test: fixing AliasedBuffer tests to enter Isolate 7 years ago
common test: print resource stack on error 7 years ago
doctool test: continue normalizing fixtures use 7 years ago
es-module build: run es-module tests in CI 7 years ago
fixtures url: fix windows drive letter handling 7 years ago
gc lib,src: fix consistent spacing inside braces 8 years ago
inspector inspector: break in eval script 7 years ago
internet dgram: added setMulticastInterface() 7 years ago
known_issues test: remove invalid test 7 years ago
message [HACK] fix message test 7 years ago
parallel [HACK] test: New test expectation for decoder. 7 years ago
pseudo-tty test: adjust indentation for stricter linting 8 years ago
pummel test: continue normalizing fixtures use 7 years ago
sequential http2: make --expose-http2 flag a non-op 7 years ago
testpy module: Allow runMain to be ESM 7 years ago
tick-processor fix --prof-process --preprocess flag 7 years ago
timers test: adjust indentation for stricter linting 8 years ago
.eslintrc.yaml tools: add eslint rule for inspector checking 7 years ago
README.md build: run es-module tests in CI 7 years ago

README.md

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.

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 to function properly.
cctest Yes C++ test that is run as part of the build process.
common Common modules shared among many tests. Documentation
es-module Yes Test ESM module loading.
fixtures Test fixtures used in various tests throughout the test suite.
gc No Tests for garbage collection related functionality.
inspector Yes Tests for the V8 inspector integration.
internet 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.
known_issues 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 known_issues.status.
message Yes Tests for messages that are output for various conditions (console.log, error messages etc.)
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 are run sequentially.
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.
timers No Tests for timing utilities (setTimeout and setInterval).

When a new test directory is added, make sure to update the CI_JS_SUITES variable in the Makefile and the js_test_suites variable in vcbuild.bat.