OSSForks/node
1
0
Fork 0
mirror of https://github.com/zebrajr/node.git synced 2025-12-06 12:20:27 +01:00
Code Issues Actions 8 Packages Projects Releases Wiki Activity
515ca295fb
node/test
History
Antoine du Hamel 646e19e2b4
test: ensure assertions are reachable in test/sequential 
PR-URL: https://github.com/nodejs/node/pull/60412
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
2025-10-29 16:29:39 +01:00
..
abort
addons test: ensure assertions are reachable in test/addons 2025-10-25 20:44:28 +02:00
async-hooks test: ensure assertions are reachable in test/async-hooks 2025-10-09 21:57:24 +00:00
benchmark test: fix typo of test-benchmark-readline.js 2025-09-30 15:21:49 +02:00
cctest test: fix small compile warning in test_network_requests_buffer.cc 2025-10-22 15:16:32 +00:00
client-proxy test: ignore EPIPE errors in https proxy invalid URL test 2025-10-18 05:43:08 +00:00
common test: split test-runner-watch-mode 2025-10-28 09:08:19 +00:00
doctool test: ensure assertions are reachable in more folders 2025-10-29 15:16:59 +00:00
embedding
es-module module: refactor and clarify async loader hook customizations 2025-10-23 13:42:23 +00:00
fixtures test: ensure assertions are reachable in more folders 2025-10-29 15:16:59 +00:00
fuzzers
internet
js-native-api test: ensure assertions are reachable in more folders 2025-10-29 15:16:59 +00:00
known_issues test: ensure assertions are reachable in more folders 2025-10-29 15:16:59 +00:00
message tools: add lint rule to ensure assertions are reached 2025-10-07 12:40:05 +00:00
module-hooks module: handle null source from async loader hooks in sync hooks 2025-10-14 16:28:22 +00:00
node-api tools: add lint rule to ensure assertions are reached 2025-10-07 12:40:05 +00:00
nop
overlapped-checker
parallel test: ensure assertions are reachable in more folders 2025-10-29 15:16:59 +00:00
pseudo-tty tools: add lint rule to ensure assertions are reached 2025-10-07 12:40:05 +00:00
pummel tools: add lint rule to ensure assertions are reached 2025-10-07 12:40:05 +00:00
report
sea test: ensure assertions are reachable in more folders 2025-10-29 15:16:59 +00:00
sequential test: ensure assertions are reachable in test/sequential 2025-10-29 16:29:39 +01:00
sqlite sqlite: fix crash session extension callbacks with workers 2025-09-23 14:41:39 +00:00
system-ca
test-runner test: split test-runner-watch-mode 2025-10-28 09:08:19 +00:00
test426
testpy build: upgrade Python linter ruff, add rules ASYNC,PERF 2025-10-08 07:37:31 +00:00
tick-processor
tools build: upgrade Python linter ruff, add rules ASYNC,PERF 2025-10-08 07:37:31 +00:00
v8-updates test: remove --always-turbofan flag 2025-10-04 18:48:39 +02:00
wasi tools: add lint rule to ensure assertions are reached 2025-10-07 12:40:05 +00:00
wasm-allocation
wpt test: fix status when compiled without inspector 2025-10-19 17:39:54 +00:00
eslint.config_partial.mjs test: ensure assertions are reachable in test/sequential 2025-10-29 16:29:39 +01:00
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. ↩︎