node/test
Anna Henningsen 6f9f546406
src: use env->RequestInterrupt() for inspector MainThreadInterface
This simplifies the code significantly, and removes the dependency of
the inspector code on the availability of a `MultiIsolatePlatform`
(by removing the dependency on a platform altogether).

It also fixes a memory leak that occurs when `RequestInterrupt()`
is used, but the interrupt handler is never called before the Isolate
is destroyed.

One downside is that this leads to a slight change in timing, because
inspector messages are not dispatched in a re-entrant way. This means
having to harden one test to account for that possibility by making
sure that the stack is always clear through a `setImmediate()`.
This does not affect the assertion made by the test, which is that
messages will not be delivered synchronously while other code is
executing.

https://github.com/nodejs/node/issues/32415

PR-URL: https://github.com/nodejs/node/pull/32523
Reviewed-By: Matheus Marchini <mat@mmarchini.me>
Reviewed-By: James M Snell <jasnell@gmail.com>
2020-04-10 17:47:14 +02:00
..
abort test: copy addons .gitignore to test/abort/ 2020-04-05 21:13:41 +02:00
addons test: skip some binding tests on IBMi PASE 2020-03-30 10:19:48 +02:00
async-hooks http: fix incorrect headersTimeout measurement 2020-04-02 14:50:20 +02:00
benchmark test: refactor all benchmark tests to use the new test option 2020-03-09 22:35:54 +01:00
cctest src: initialize inspector before RunBootstrapping() 2020-04-08 00:04:55 +02:00
common src,cli: support compact (one-line) JSON reports 2020-03-17 08:42:41 -07:00
doctool test: fix tool path in test-doctool-versions.js 2020-04-05 21:18:31 +02:00
embedding test: use common.buildType in embedding test 2020-03-27 17:29:41 +01:00
es-module module: expose exports conditions to loaders 2020-04-03 01:29:39 +02:00
fixtures module: expose exports conditions to loaders 2020-04-03 01:29:39 +02:00
internet test: fix flaky test-dns-any.js 2020-03-02 07:02:51 -08:00
js-native-api src: remove calls to deprecated ArrayBuffer methods 2020-03-21 12:00:57 +01:00
known_issues test: skip crypto test on arm buildbots 2020-04-04 07:09:51 -07:00
message esm: port loader code to JS 2020-03-13 17:34:43 +01:00
node-api n-api: detect deadlocks in thread-safe function 2020-04-09 02:41:28 -07:00
parallel src: use env->RequestInterrupt() for inspector MainThreadInterface 2020-04-10 17:47:14 +02:00
pseudo-tty test: fix flaky test-trace-sigint-on-idle 2020-02-09 22:16:23 +01:00
pummel test: use Promise.all() in test-hash-seed 2020-03-17 18:29:56 -07:00
report report: fix stderr matching for fatal error 2020-04-09 06:45:48 +00:00
sequential test: make sure that inspector tests finish 2020-04-08 16:43:13 +02:00
testpy
tick-processor
tools
v8-updates deps: update V8 dtrace & postmortem metadata 2020-03-18 16:23:32 -07:00
wasi test: skip a wasi test on IBMi PASE 2020-03-30 17:08:43 +02:00
wpt
.eslintrc.yaml lib,tools,test: remove custom number-isnan rule 2020-01-08 00:22:25 -05:00
README.md
root.status test: add test-worker-prof to the SLOW list for debug 2020-04-01 10:39:38 -04:00

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 for when the --abort-on-uncaught-exception flag is used.
addons Yes Tests for addon functionality along with some tests that require an addon.
async-hooks Yes Tests for async_hooks functionality.
benchmark No 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 Common modules shared among many tests. Documentation
doctool Yes Tests for the documentation generator.
es-module Yes Test ESM module loading.
fixtures Test fixtures used in various tests throughout the test suite.
internet No Tests that make real outbound network connections. Tests for networking related modules may also be present in other directories, but those tests do not make outbound connections.
js-native-api Yes Tests for Node.js-agnostic n-api functionality.
known_issues Yes Tests reproducing known issues within the system. 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.
message Yes Tests for messages that are output for various conditions (console.log, error messages etc.)
node-api Yes Tests for Node.js-specific n-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 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.
v8-updates No Tests for V8 performance integration.