mirrors/nodejs
mirrors/nodejs
0
0
Fork 0
mirror of https://github.com/nodejs/node.git synced 2024-11-30 07:27:22 +01:00
Code Issues Releases Activity
21c3a402d4
nodejs/test
History
Ruben Bridgewater 21c3a402d4
assert: validate input stricter 
This makes sure invalid `error` objects are not ignored when using
`assert.throws` and `assert.rejects`.

PR-URL: https://github.com/nodejs/node/pull/20481
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
2018-05-10 15:27:32 +02:00
..
abort
addons
addons-napi src: add environment cleanup hooks 2018-05-10 14:15:16 +02:00
async-hooks timers: reschedule interval even if it threw 2018-04-29 16:51:05 +02:00
cctest src: refactor BaseObject internal field management 2018-05-04 00:57:39 +02:00
common tools: add eslint check for skipIfEslintMissing 2018-05-08 10:43:26 -04:00
doctool tools: remove redundant code in doc/html.js 2018-05-07 10:43:43 +02:00
es-module
fixtures http2: fix responses to long payload reqs 2018-04-28 18:17:28 +02:00
gc
internet
known_issues
message assert: make sure throws is able to handle primitives 2018-05-10 14:14:23 +02:00
parallel assert: validate input stricter 2018-05-10 15:27:32 +02:00
pseudo-tty src: remove kFlagNoShutdown flag 2018-05-04 00:57:38 +02:00
pummel
sequential fs: move fs/promises to fs.promises 2018-05-07 19:47:42 -04:00
testpy
tick-processor
timers
.eslintrc.yaml tools: add eslint check for skipIfEslintMissing 2018-05-08 10:43:26 -04:00
README.md

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.