0
0
mirror of https://github.com/nodejs/node.git synced 2024-11-29 23:16:30 +01:00
nodejs/test
Luigi Pinca 96e82beac3 test: fix test-http-dump-req-when-res-ends
Fix test-http-dump-req-when-res-ends and move it back to test/parallel/

PR-URL: https://github.com/nodejs/node/pull/19866
Refs: https://github.com/nodejs/node/pull/19823
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
2018-04-11 09:30:02 +02:00
..
abort
addons src: rename ERR_STRING_TOO_LARGE to ERR_STRING_TOO_LONG 2018-04-10 01:08:10 +02:00
addons-napi n-api: add more int64_t tests 2018-04-08 11:31:12 -07:00
async-hooks
cctest inspector: report client-visible host and port 2018-04-02 10:20:30 -07:00
common test: fix multiple expectedWarnings bug 2018-04-06 03:14:08 +02:00
doctool
es-module module: fix e.stack error when throwing undefined or null 2018-04-10 00:47:12 +02:00
fixtures module: fix e.stack error when throwing undefined or null 2018-04-10 00:47:12 +02:00
gc
internet test: verify inspector help url works 2018-04-10 15:42:32 -04:00
known_issues
message
parallel test: fix test-http-dump-req-when-res-ends 2018-04-11 09:30:02 +02:00
pseudo-tty
pummel tools: add 'spaced-comment' into eslint rules 2018-04-01 22:33:13 +08:00
sequential test: fix test-http-dump-req-when-res-ends 2018-04-11 09:30:02 +02: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.