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.
 
 
 
 
 
 
Daniel Bevenius 60f0dc7d42 src: rename CONNECTION provider to SSLCONNECTION 8 years ago
..
abort test: add abort test for backtrace validation 9 years ago
addons test: add not-called check to heap-profiler test 8 years ago
addons-napi test: add common.mustCall() to NAPI exception test 8 years ago
async-hooks src: rename CONNECTION provider to SSLCONNECTION 8 years ago
cctest inspector: handle socket close before close frame 8 years ago
common test: make the rest of tests path-independent 8 years ago
debugger test: reduce string concatenations 8 years ago
disabled test: enable test-debugger-pid 8 years ago
doctool test: make tests cwd-independent 8 years ago
fixtures fs: throw on invalid callbacks for async functions 8 years ago
gc test: reduce string concatenations 8 years ago
inspector inspector: report when main context is destroyed 8 years ago
internet dns: support promisified `lookup(Service)` 8 years ago
known_issues test: make the rest of tests path-independent 8 years ago
message lib: implement async_hooks API in core 8 years ago
parallel test: use mustCall in tls-connect-given-socket 8 years ago
pseudo-tty test: reduce string concatenations 8 years ago
pummel test: reduce string concatenations 8 years ago
sequential test: make the rest of tests path-independent 8 years ago
testpy test: adding tests for initHooks API 8 years ago
tick-processor test: move tick-processor tests to own directory 8 years ago
timers test: use eslint to fix var->const/let 8 years ago
.eslintrc.yaml tools: add rule prefering common.mustNotCall() 8 years ago
README.md test: move WPT to its own testing module 8 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 direcotry, see the contributing guide.

Test Directories

Directory Runs on CI Purpose
abort No 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]
debugger No Tests for debugger functionality along with some tests that require an addon to function properly.
disabled No Tests that have been disabled from running for various reasons.
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).