mirrors/nodejs
mirrors/nodejs
0
0
Fork 0
mirror of https://github.com/nodejs/node.git synced 2024-11-29 23:16:30 +01:00
Code Issues Releases Activity
c2d63a9785
nodejs/test
History
Patrick Heneise 8215c671d3 test: refactor fs.write() test 
PR-URL: https://github.com/nodejs/node/pull/16827
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
2017-11-13 11:23:45 +05:30
..
abort
addons tls: implement clientCertEngine option 2017-11-11 13:35:23 -08:00
addons-napi test: improve error emssage reporting in testNapiRun.js 2017-11-08 13:58:56 +00:00
async-hooks test: show incorrect value on test failure 2017-11-07 09:47:55 +00:00
cctest src: prepare v8 platform for multi-isolate support 2017-11-12 14:01:54 +01:00
common test: introduce test/common/internet.addresses 2017-11-08 18:54:08 +08:00
doctool
es-module loader: test search module 2017-11-12 10:54:11 -08:00
fixtures test: change concatenated string to template 2017-11-11 12:03:40 +01:00
gc
internet test: use internet.addresses in internet tests 2017-11-08 18:54:20 +08:00
known_issues
message
parallel test: refactor fs.write() test 2017-11-13 11:23:45 +05:30
pseudo-tty
pummel test: use ES6 classes instead of util.inherits 2017-11-12 10:29:45 -08:00
sequential lib: improve the usage of TypeError[INVALID_ARG_TYPE] 2017-11-12 11:04:06 -08:00
testpy
tick-processor
timers
.eslintrc.yaml
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.