lukechilds
/
node
mirror of https://github.com/lukechilds/node.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
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.
18891 Commits
131 Branches
446 Tags
325 MiB
 
 
 
 
 
 
Tree: 6f1caadb85
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '6f1caadb85'
${ noResults }
node/test
Bryan English 6f1caadb85
tls: prefer path over port in connect 		8 years ago
..
abort test,process: run 'abort' suite on Windows 7 years ago
addons build: enable runtime linking 7 years ago
addons-napi n-api: remove n-api module loading flag 7 years ago
async-hooks async_hooks,doc: some async_hooks improvements 7 years ago
cctest src: refactor `#include` handling 7 years ago
common test: allow adding known-globals through ENV 7 years ago
doctool test: continue normalizing fixtures use 7 years ago
es-module module: Allow runMain to be ESM 7 years ago
fixtures test: do not write fixture in test-require-symlink 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 test: remove faulty test case 7 years ago
parallel tls: prefer path over port in connect 7 years ago
pseudo-tty test: adjust indentation for stricter linting 8 years ago
pummel test: continue normalizing fixtures use 7 years ago
sequential test: fix flaky test-http2-session-timeout 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 test: remove obsolete debugger tests 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 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
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).