mirrors/nodejs
mirrors/nodejs
0
0
Fork 0
mirror of https://github.com/nodejs/node.git synced 2024-11-27 22:16:50 +01:00
Code Issues Releases Activity
e92499c963
nodejs/test
History
Thomas Chetwin e92499c963
test: convert readdir test to use test runner 
Signed-off-by: tchetwin <tchetwin@bloomberg.net>
PR-URL: https://github.com/nodejs/node/pull/55750
Reviewed-By: Pietro Marchini <pietro.marchini94@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
2024-11-23 21:23:53 +00:00
..
abort
addons
async-hooks
benchmark
cctest
common report: fix network queries in getReport libuv with exclude-network 2024-11-12 15:57:59 +00:00
doctool
embedding
es-module module: do not warn when require(esm) comes from node_modules 2024-11-23 11:28:47 +00:00
fixtures module: do not warn when require(esm) comes from node_modules 2024-11-23 11:28:47 +00:00
fuzzers
internet
js-native-api
known_issues
message
node-api
overlapped-checker
parallel test: convert readdir test to use test runner 2024-11-23 21:23:53 +00:00
pseudo-tty
pummel crypto: allow length=0 for HKDF and PBKDF2 in SubtleCrypto.deriveBits 2024-11-17 13:13:47 +00:00
report report: fix network queries in getReport libuv with exclude-network 2024-11-12 15:57:59 +00:00
sequential fs: remove dirent.path 2024-11-15 00:18:05 +01:00
testpy
tick-processor
tools
v8-updates
wasi
wasm-allocation
wpt crypto: allow non-multiple of 8 in SubtleCrypto.deriveBits 2024-11-23 08:22:12 -08:00
eslint.config_partial.mjs
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 run on Windows, be sure to clone Node.js source code with the autocrlf git config flag set to true.

Test Directories

Directory Runs on CI Purpose
abort Yes Tests that use --abort-on-uncaught-exception and other cases where we want to avoid generating a core file.
addons Yes Tests for addon functionality along with some tests that require an addon.
async-hooks Yes Tests for async_hooks functionality.
benchmark Yes Test minimal functionality of benchmarks.
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 N/A Common modules shared among many tests.1
doctool Yes Tests for the documentation generator.
es-module Yes Test ESM module loading.
fixtures N/A Test fixtures used in various tests throughout the test suite.
internet No Tests that make real outbound network connections.2
js-native-api Yes Tests for Node.js-agnostic Node-API functionality.
known_issues Yes Tests reproducing known issues within the system.3
message Yes Tests for messages that are output for various conditions
node-api Yes Tests for Node.js-specific Node-API functionality.
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 must not run in parallel.
testpy N/A Test configuration utility used by various test suites.
tick-processor No Tests for the V8 tick processor integration.4
v8-updates No Tests for V8 performance integration.

  1. Documentation ↩︎

  2. Tests for networking related modules may also be present in other directories, but those tests do not make outbound connections. ↩︎

  3. All tests inside of this directory are expected to fail. If a test doesn't fail on certain platforms, those should be skipped via known_issues.status. ↩︎

  4. 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. ↩︎