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.
 
 
 
 
 
 
Miguel Angel Asencio Hurtado 9a5c3cf185
test: continue normalizing fixtures use
7 years ago
..
abort test: run abort tests 7 years ago
addons test: extend async addon test 7 years ago
addons-napi n-api: implement promise 7 years ago
async-hooks test: continue normalizing fixtures use 7 years ago
cctest src: Node implementation of v8::Platform 7 years ago
common test, win: fix IPv6 detection on Windows 7 years ago
debugger lib,src: fix consistent spacing inside braces 8 years ago
doctool test: continue normalizing fixtures use 7 years ago
fixtures test: continue normalizing fixtures use 7 years ago
gc lib,src: fix consistent spacing inside braces 8 years ago
inspector test: continue normalizing fixtures use 7 years ago
internet test: continue normalizing fixtures use 7 years ago
known_issues test: continue normalizing fixtures use 7 years ago
message lib: instantiate console methods eagerly 7 years ago
parallel http2: refactor error handling 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: continue normalizing fixtures use 7 years ago
testpy test: run abort tests 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: remove legacy indentation linting 8 years ago
README.md test: remove disabled tests directory 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 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
debugger No Tests for debuggerfunctionality along with some tests that require an addon to function properly.
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).