0
0
mirror of https://github.com/nodejs/node.git synced 2024-11-29 23:16:30 +01:00
nodejs/test
Rich Trott 4dd7d09723
test: skip test-fs-readdir-ucs2 if no support
If the filesystem does not support UCS2, do not run the test.

PR-URL: https://github.com/nodejs/node/pull/14029
Fixes: https://github.com/nodejs/node/issues/14028
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
2017-07-04 08:00:35 -04:00
..
abort test: simplify test skipping 2017-07-04 12:41:49 +03:00
addons test: simplify test skipping 2017-07-04 12:41:49 +03:00
addons-napi n-api: add napi_delete_property() 2017-07-01 11:40:14 -04:00
async-hooks test: simplify test skipping 2017-07-04 12:41:49 +03:00
cctest test: check uv_ip4_addr return value 2017-06-26 10:28:13 -07:00
common test: simplify test skipping 2017-07-04 12:41:49 +03:00
debugger
disabled test: replace indexOf with includes and startsWith 2017-07-02 23:36:39 +02:00
doctool test: simplify test skipping 2017-07-04 12:41:49 +03:00
fixtures test: simplify test skipping 2017-07-04 12:41:49 +03:00
gc
inspector test: simplify test skipping 2017-07-04 12:41:49 +03:00
internet test: simplify test skipping 2017-07-04 12:41:49 +03:00
known_issues test: simplify test skipping 2017-07-04 12:41:49 +03:00
message test: remove common.noop 2017-07-03 11:39:35 -07:00
parallel test: skip test-fs-readdir-ucs2 if no support 2017-07-04 08:00:35 -04:00
pseudo-tty test: remove common.noop 2017-07-03 11:39:35 -07:00
pummel test: simplify test skipping 2017-07-04 12:41:49 +03:00
sequential test: simplify test skipping 2017-07-04 12:41:49 +03:00
testpy
tick-processor test: simplify test skipping 2017-07-04 12:41:49 +03:00
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 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.
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).