Google Git
Sign in
chromium / external / github.com / v8 / node / refs/heads/node-ci-2025-11-20 / . / test
tree: bfe310227fc24a8a8404df087cd7ac8b769d54e1 [path history] [tgz]
  1. abort/
  2. addons/
  3. async-hooks/
  4. benchmark/
  5. cctest/
  6. client-proxy/
  7. common/
  8. doctool/
  9. embedding/
  10. es-module/
  11. fixtures/
  12. fuzzers/
  13. internet/
  14. js-native-api/
  15. known_issues/
  16. message/
  17. module-hooks/
  18. node-api/
  19. nop/
  20. overlapped-checker/
  21. parallel/
  22. pseudo-tty/
  23. pummel/
  24. report/
  25. sea/
  26. sequential/
  27. sqlite/
  28. system-ca/
  29. test-runner/
  30. test426/
  31. testpy/
  32. tick-processor/
  33. tools/
  34. v8-updates/
  35. wasi/
  36. wasm-allocation/
  37. wpt/
  38. eslint.config_partial.mjs
  39. README.md
  40. root.status
test/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

DirectoryRuns on CIPurpose
abortYesTests that use --abort-on-uncaught-exception and other cases where we want to avoid generating a core file.
addonsYesTests for addon functionality along with some tests that require an addon.
async-hooksYesTests for async_hooks functionality.
benchmarkYesTest minimal functionality of benchmarks.
cctestYesC++ tests that are run as part of the build process.
code-cacheNoTests for a Node.js binary compiled with V8 code cache.
commonN/ACommon modules shared among many tests.^1
doctoolYesTests for the documentation generator.
es-moduleYesTest ESM module loading.
fixturesN/ATest fixtures used in various tests throughout the test suite.
internetNoTests that make real outbound network connections.[^2]
js-native-apiYesTests for Node.js-agnostic Node-API functionality.
known_issuesYesTests reproducing known issues within the system.[^3]
messageYesTests for messages that are output for various conditions
node-apiYesTests for Node.js-specific Node-API functionality.
parallelYesVarious tests that are able to be run in parallel.
pseudo-ttyYesTests that require stdin/stdout/stderr to be a TTY.
pummelNoVarious tests for various modules / system functionality operating under load.
sequentialYesVarious tests that must not run in parallel.
testpyN/ATest configuration utility used by various test suites.
tick-processorNoTests for the V8 tick processor integration.[^4]
v8-updatesNoTests for V8 performance integration.

[^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/main/prof_process.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.