mirrors/nodejs
mirrors/nodejs
0
0
Fork 0
mirror of https://github.com/nodejs/node.git synced 2024-12-01 16:10:02 +01:00
Code Issues Releases Activity
5c8937c3c6
nodejs/test
History
Michaël Zasso 5c8937c3c6 test: fix esm message tests after V8 update 
PR-URL: https://github.com/nodejs/node/pull/18453
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Yang Guo <yangguo@chromium.org>
Reviewed-By: Ali Ijaz Sheikh <ofrobots@google.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
2018-03-07 16:48:52 +01:00
..
abort
addons test: specify 'dir' for directory symlinks 2018-03-01 15:47:29 -08:00
addons-napi n-api: update reference test 2018-03-04 16:34:29 -05:00
async-hooks test,benchmark: use new Buffer API where appropriate 2018-03-04 12:50:15 +01:00
cctest build: add node_lib_target_name to cctest deps 2018-02-19 12:27:25 +01:00
common lib,test: remove yoda statements 2018-03-04 15:33:18 +01:00
doctool
es-module lib: port remaining errors to new system 2018-03-07 14:54:38 +01:00
fixtures loader: fix --inspect-brk 2018-03-01 09:18:30 -06:00
gc
internet test: minor refactoring 2018-02-16 16:54:07 +01:00
known_issues
message test: fix esm message tests after V8 update 2018-03-07 16:48:52 +01:00
parallel test: update postmortem metadata test 2018-03-07 16:48:52 +01:00
pseudo-tty test: really test the ttywrap bits of getasyncid 2018-02-22 12:12:41 -05:00
pummel lib,test: remove yoda statements 2018-03-04 15:33:18 +01:00
sequential http2: refer to stream errors by name 2018-03-04 13:52:31 +01:00
testpy
tick-processor tools, test: fix prof polyfill readline 2018-02-17 10:06:53 -02:00
timers
.eslintrc.yaml lint: move eslint to new plugin system 2018-02-20 13:13:22 -06:00
README.md

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.
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.