Nodejs/node
1
0
Fork 0
mirror of https://github.com/nodejs/node.git synced 2024-11-21 10:59:27 +00:00
Code Issues Actions 25 Packages Projects Releases Wiki Activity
34f164f1c2
node/test
History
Jerome Covington 878f587783 test: assert that invalidcmd throws error code 
Update invalidcmd test case in test-child-process-spawn-typeerror to
assert on specific expected error code.

PR-URL: https://github.com/nodejs/node/pull/23942
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
2018-11-01 20:25:01 -07:00
..
abort
addons test: verify performance.timerify() works w/ non-Node Contexts 2018-10-25 19:49:46 +02:00
addons-napi
async-hooks
cctest
code-cache test: run code cache test by default and test generator 2018-10-30 14:38:27 +08:00
common
doctool
es-module
fixtures child_process: handle undefined/null for fork() args 2018-11-01 19:41:33 -07:00
internet
known_issues module: support multi-dot file extension 2018-11-01 19:28:15 -07:00
message
parallel test: assert that invalidcmd throws error code 2018-11-01 20:25:01 -07:00
pseudo-tty
pummel
sequential test: fix test-fs-watch-system-limit 2018-11-01 19:07:24 -07:00
testpy
tick-processor
v8-updates
.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 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.
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.