0
0
mirror of https://github.com/nodejs/node.git synced 2024-12-01 16:10:02 +01:00
nodejs/test
Anatoli Papirovski 38ee25e2e2
child_process: do not ignore proto values of env
This reverts this behaviour introduced in a recent PR, and updates
the test. Without this change, CitGM and other packages are broken.

PR-URL: https://github.com/nodejs/node/pull/18210
Fixes: https://github.com/nodejs/citgm/issues/536
Reviewed-By: Evan Lucas <evanlucas@me.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
2018-01-18 08:04:06 -05:00
..
abort test: fix spelling in test case comments 2018-01-11 16:49:38 +01:00
addons build: refine static and shared lib build 2018-01-17 11:34:28 +08:00
addons-napi test: fixed typos in napi test 2018-01-17 08:41:53 +08:00
async-hooks src,doc,test: Fix common misspellings 2018-01-16 23:44:27 +01:00
cctest
common src,doc,test: Fix common misspellings 2018-01-16 23:44:27 +01:00
doctool tools: move eslint from tools to tools/node_modules 2018-01-11 09:48:05 +01:00
es-module module: refactor loader 2018-01-15 12:42:29 -06:00
fixtures test: use shorthand properties 2018-01-17 14:33:20 +01:00
gc
internet test: remove trivial buffer imports 2018-01-18 01:14:09 +08:00
known_issues test: remove orphaned entries from status 2018-01-11 09:59:44 -08:00
message test: improve to use template string 2018-01-17 08:50:02 +08:00
parallel child_process: do not ignore proto values of env 2018-01-18 08:04:06 -05:00
pseudo-tty
pummel test: use shorthand properties 2018-01-17 14:33:20 +01:00
sequential test: fix flaky interval test 2018-01-18 01:11:27 +08:00
testpy
tick-processor
timers
.eslintrc.yaml
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.