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
9fbf0c60b5
nodejs/test
History
Anna Henningsen 9fbf0c60b5
worker: use copy of process.env 
Instead of sharing the OS-backed store for all `process.env` instances,
create a copy of `process.env` for every worker that is created.

The copies do not interact. Native-addons do not see modifications to
`process.env` from Worker threads, but child processes started from
Workers do default to the Worker’s copy of `process.env`.

This makes Workers behave like child processes as far as `process.env`
is concerned, and an option corresponding to the `child_process`
module’s `env` option is added to the constructor.

Fixes: https://github.com/nodejs/node/issues/24947

PR-URL: https://github.com/nodejs/node/pull/26544
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Yongsheng Zhang <zyszys98@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
2019-03-30 22:25:35 +01:00
..
abort
addons esm: phase two of new esm implementation 2019-03-27 15:52:11 -04:00
async-hooks benchmark,doc,lib: capitalize more comments 2019-03-27 17:20:06 +01:00
benchmark
cctest
code-cache
common test: move hasCrypto check 2019-03-29 10:58:42 +01:00
doctool
es-module esm: phase two of new esm implementation 2019-03-27 15:52:11 -04:00
fixtures crypto: decode missing passphrase errors 2019-03-30 10:31:43 +01:00
internet
js-native-api benchmark,doc,lib: capitalize more comments 2019-03-27 17:20:06 +01:00
known_issues test: add known_issues test for fs.copyFile() 2019-03-29 19:17:16 -07:00
message esm: phase two of new esm implementation 2019-03-27 15:52:11 -04:00
node-api
parallel worker: use copy of process.env 2019-03-30 22:25:35 +01:00
pseudo-tty
pummel benchmark,doc,lib: capitalize more comments 2019-03-27 17:20:06 +01:00
report
sequential benchmark,doc,lib: capitalize more comments 2019-03-27 17:20:06 +01:00
testpy
tick-processor
v8-updates test: update postmortem metadata test for V8 7.4 2019-03-28 16:39:35 -04:00
wpt
.eslintrc.yaml
README.md
root.status tools: remove eslint rule no-let-in-for-declaration 2019-03-26 09:46:41 -07:00

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.

For the tests to successfully run on Windows, Node.js has to be checked out from GitHub with the autocrlf git config flag set to true.

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.
async-hooks Yes Tests for async_hooks functionality.
benchmark No Test minimal functionality of benchmarks.
cctest Yes C++ tests that are run as part of the build process.
code-cache No Tests for a Node.js binary compiled with V8 code cache.
common Common modules shared among many tests. Documentation
doctool Yes Tests for the documentation generator.
es-module Yes Test ESM module loading.
fixtures Test fixtures used in various tests throughout the test suite.
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.
js-native-api Yes Tests for Node.js-agnostic n-api functionality.
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.)
node-api Yes Tests for Node.js-specific n-api functionality.
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.
v8-updates No Tests for V8 performance integration.