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
e6a55b4391
nodejs/test
History
Robert Nagy 2bfb3403ed
stream: avoid destroying writable source 
User might still want to be able to use the writable side
of src. This is in the case where e.g. the Duplex input
is not directly connected to its output. Such a case could
happen when the Duplex is reading from a socket and then echos
the data back on the same socket.

PR-URL: https://github.com/nodejs/node/pull/32198
Refs: 4d93e105bf (commitcomment-37751035)
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
2020-03-11 20:57:42 -04:00
..
abort
addons
async-hooks async_hooks: avoid resource reuse by FileHandle 2020-03-11 19:26:10 +01:00
benchmark test: refactor all benchmark tests to use the new test option 2020-03-09 22:35:54 +01:00
cctest src: introduce node_sockaddr 2020-03-05 12:07:34 -08:00
common benchmark: add test and all options and improve errors" 2020-03-09 22:35:53 +01:00
doctool
es-module
fixtures test: use index.js if package.json "main" is empty 2020-03-09 13:23:16 +01:00
internet test: fix flaky test-dns-any.js 2020-03-02 07:02:51 -08:00
js-native-api n-api: define release 6 2020-03-09 11:58:51 -07:00
known_issues test: always skip vm-timeout-escape-queuemicrotask 2020-03-10 11:49:09 -07:00
message
node-api n-api: define release 6 2020-03-09 11:58:51 -07:00
parallel stream: avoid destroying writable source 2020-03-11 20:57:42 -04:00
pseudo-tty
pummel
report
sequential test: mark test-timers-blocking-callback flaky on osx 2020-03-11 10:31:46 -04:00
testpy
tick-processor
tools
v8-updates
wasi test: add WASI test for path_link() 2020-03-08 15:11:46 -04:00
wpt
.eslintrc.yaml
README.md
root.status

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 run on Windows, be sure to clone Node.js source code 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.
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 network connections. 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. 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 must not run in parallel.
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.