node/test
Joyee Cheung f993fca4e4
test: deflake sequential/test-tls-session-timeout
This patch:

- Splits the validation tests into a separate file and keep the
  test focus on functional test of the sessionTimeout option.
- Increase the testing timeout to 5 seconds in case it takes too
  long for the first connection to complete and the session is
  already expired when the second connection is started.
- Use a specific `sessionIdContext` to ensure stable session ID.
- Fix the s_client arguments by specifying CA file and server name.
- Do not use the serialized session ticket for the first connection.
  That was genearted years ago and may not work in different OpenSSL
  versions. Let the first fresh connection generate the ticket.
- Use random port instead of the common port.
- Add a timeout before the second connection to ensure session ticket
  is properly written.
- Log information to faciliate debugging.

PR-URL: https://github.com/nodejs/node/pull/59423
Fixes: https://github.com/nodejs/node/issues/26839
Reviewed-By: Juan José Arboleda <soyjuanarbol@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Jacob Smith <jacob@frende.me>
Reviewed-By: Stefan Stojanovic <stefan.stojanovic@janeasystems.com>
2025-08-11 17:36:30 +00:00
..
abort
addons test: expand linting rules around assert w literal messages 2025-07-23 16:28:06 +00:00
async-hooks meta: enable jsdoc/check-tag-names rule 2025-07-18 09:28:21 +00:00
benchmark test: skip tests that cause timeouts on IBM i 2025-07-21 14:38:20 +00:00
cctest quic: fixup NO_ERROR macro conflict on windows 2025-08-06 19:33:03 -07:00
client-proxy cli: add --use-env-proxy 2025-07-26 20:43:10 +00:00
common test: split test-fs-cp.js 2025-08-10 19:35:42 +00:00
doctool
embedding
es-module esm: unflag --experimental-wasm-modules 2025-07-22 13:24:06 -07:00
fixtures test: exclude mock from coverage 2025-08-11 05:49:53 +00:00
fuzzers
internet dns: move falsy hostname in lookup to end-of-life 2025-06-13 12:47:23 +00:00
js-native-api test: expand linting rules around assert w literal messages 2025-07-23 16:28:06 +00:00
known_issues test: add known issue test for fs.cpSync dereference bug 2025-08-02 14:23:15 +00:00
message lib: restructure assert to become a class 2025-08-05 14:15:02 +00:00
module-hooks module: fix conditions override in synchronous resolve hooks 2025-07-26 09:13:11 +00:00
node-api
nop process: make execve's args argument optional 2025-07-26 02:35:57 +00:00
overlapped-checker
parallel test: deflake sequential/test-tls-session-timeout 2025-08-11 17:36:30 +00:00
pseudo-tty lib: add trace-sigint APIs 2025-08-11 09:14:44 +00:00
pummel test: deflake test-buffer-large-size-buffer-alloc-unsafe 2025-06-22 09:43:35 +00:00
report test: expand linting rules around assert w literal messages 2025-07-23 16:28:06 +00:00
sequential test: deflake sequential/test-tls-session-timeout 2025-08-11 17:36:30 +00:00
sqlite
system-ca cli: add NODE_USE_SYSTEM_CA=1 2025-08-10 14:20:58 +00:00
test426
testpy tools: support environment variables via comments 2025-05-11 17:54:56 +00:00
tick-processor
tools
v8-updates
wasi lib: expose setupInstance method on WASI class 2025-07-07 08:41:16 -07:00
wasm-allocation test: skip wasm-allocation tests for pointer compression builds 2025-05-18 23:24:02 +00:00
wpt test: update WPT resources,WebCryptoAPI,webstorage 2025-08-03 11:31:39 +00:00
eslint.config_partial.mjs test: expand linting rules around assert w literal messages 2025-07-23 16:28:06 +00:00
README.md
root.status

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