0
0
mirror of https://github.com/nodejs/node.git synced 2024-11-29 15:06:33 +01:00
nodejs/test
timothy searcy f051737ee4 test: test and docs for detached fork process
This tests child process fork component in detached mode
by spawning a parent process that creates a child process.
We kill the parent process and check if the child is still
running.

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

PR-URL: https://github.com/nodejs/node/pull/24524
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
2018-11-28 11:14:37 -08:00
..
abort
addons
addons-napi n-api,test: remove last argument in assert.strictEqual() 2018-11-27 22:22:37 -08:00
async-hooks http,https: protect against slow headers attack 2018-11-28 11:36:34 +11:00
benchmark benchmark: support URL inputs in create-clientrequest 2018-11-20 05:14:36 +08:00
cctest
code-cache src: use STL containers instead of v8 values for static module data 2018-11-20 01:17:15 +08:00
common test: remove unused reject handlers 2018-11-22 03:39:15 -08:00
doctool tools,doc: fix version picker bug in html.js 2018-11-27 19:14:54 -08:00
es-module
fixtures test: test and docs for detached fork process 2018-11-28 11:14:37 -08:00
internet
known_issues test: replcae anonymous closure with arrow function 2018-11-22 05:46:06 +01:00
message test: use print() function on both Python 2 and 3 2018-11-19 16:10:29 -05:00
parallel test: test and docs for detached fork process 2018-11-28 11:14:37 -08:00
pseudo-tty console: lazy load process.stderr and process.stdout 2018-11-29 01:52:54 +08:00
pummel test: convert callback to arrow function 2018-11-25 19:45:25 +05:30
sequential http: fix header limit errors and test for llhttp 2018-11-28 11:36:34 +11:00
testpy
tick-processor test: use destructuring on require 2018-11-24 10:56:04 +09:00
v8-updates
wpt test: use Worker scope in WPT 2018-11-20 15:27:38 -08:00
.eslintrc.yaml
README.md
root.status

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.
addons-napi Yes Tests for n-api functionality.
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.
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.
v8-updates No Tests for V8 performance integration.