0
0
mirror of https://github.com/nodejs/node.git synced 2024-12-01 16:10:02 +01:00
nodejs/test
Robert Nagy 2361b5c041 stream: forward writableObjectMode
Duplex did not properly forward writableObjectMode.

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

PR-URL: https://github.com/nodejs/node/pull/33390
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
2020-05-19 00:02:32 +02:00
..
abort
addons buffer,n-api: release external buffers from BackingStore callback 2020-05-16 12:15:07 +02:00
async-hooks tools: enable no-else-return lint rule 2020-05-16 06:42:16 +02:00
benchmark
cctest
common tools: enable no-else-return lint rule 2020-05-16 06:42:16 +02:00
doctool
embedding
es-module module: add specific error for dir import 2020-05-15 19:08:39 -07:00
fixtures module: do not check circular dependencies for exported proxies 2020-05-15 01:55:28 +02:00
internet test: fix test-dns-idna2008 2020-05-15 05:48:48 -07:00
js-native-api
known_issues
message
node-api buffer,n-api: release external buffers from BackingStore callback 2020-05-16 12:15:07 +02:00
parallel stream: forward writableObjectMode 2020-05-19 00:02:32 +02:00
pseudo-tty
pummel tools: enable no-else-return lint rule 2020-05-16 06:42:16 +02:00
report
sequential tools: add eslint rule to only pass through 'test' to debuglog 2020-05-10 14:00:37 +02:00
testpy
tick-processor
tools
v8-updates
wasi wasi: prevent syscalls before start 2020-05-08 01:02:19 +02:00
wpt test: update WPT interfaces and hr-time 2020-05-13 22:09:58 +08:00
.eslintrc.yaml tools: add eslint rule to only pass through 'test' to debuglog 2020-05-10 14:00:37 +02:00
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 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.