node/test
Brian White 8080a9bf40
http: fix error check in Execute()
Refs: https://github.com/nodejs/node/pull/24738
Fixes: https://github.com/nodejs/node/issues/25858

PR-URL: https://github.com/nodejs/node/pull/25939
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com>
2019-03-11 14:38:28 +00:00
..
abort test: fix spelling in test case comments 2018-03-29 23:25:33 -04:00
addons n-api: use module name macro 2018-04-16 17:46:09 -04:00
addons-napi n-api: add more int64_t tests 2018-04-16 17:46:19 -04:00
cctest inspector: check Host header 2018-03-28 02:13:14 -04:00
common n-api: add code parameter to error helpers 2018-04-16 17:46:01 -04:00
debugger
disabled
doctool test: include expected result in error messages 2017-10-25 04:09:45 -04:00
fixtures test: update certificates and private keys 2018-08-13 20:59:17 +10:00
gc
inspector inspector: don't bind to 0.0.0.0 by default 2018-08-13 21:01:13 +10:00
internet dgram: added setMulticastInterface() 2018-02-12 19:28:05 -05:00
known_issues test: remove orphaned entries from status 2018-03-29 23:25:35 -04:00
message test: improve to use template string 2018-02-27 00:43:25 -05:00
parallel http: fix error check in Execute() 2019-03-11 14:38:28 +00:00
pseudo-tty test: add coverage to tty module 2017-12-13 15:53:45 +00:00
pummel test: improve to use template string 2018-02-27 00:43:25 -05:00
sequential cli: add --max-http-header-size flag 2018-12-21 18:40:56 -05:00
testpy n-api: add support for abi stable module API 2018-04-16 17:45:48 -04:00
tick-processor
timers
.eslintrc.yaml tools: add number-isnan rule 2018-02-26 22:56:42 -05: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 direcotry, see the contributing guide.

Test Directories

Directory Runs on CI Purpose
abort No 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]
debugger No Tests for debugger functionality along with some tests that require an addon to function properly.
disabled No Tests that have been disabled from running for various reasons.
fixtures Test fixtures used in various tests throughout the test suite.
gc No Tests for garbage collection related functionality.
inspector Yes Tests for the V8 inspector integration.
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.
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).