tree: 6bff9bc07430cd75bf0803e234a76a055f8a0074 [path history] [tgz]
  1. .eslintrc.yaml
  2. README.md
  3. abort/
  4. addons/
  5. async-hooks/
  6. benchmark/
  7. cctest/
  8. code-cache/
  9. common/
  10. doctool/
  11. es-module/
  12. fixtures/
  13. internet/
  14. js-native-api/
  15. known_issues/
  16. message/
  17. node-api/
  18. parallel/
  19. pseudo-tty/
  20. pummel/
  21. report/
  22. root.status
  23. sequential/
  24. testpy/
  25. tick-processor/
  26. v8-updates/
  27. wpt/
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 successfully run on Windows, Node.js has to be checked out from GitHub with the autocrlf git config flag set to true.

Test Directories

DirectoryRuns on CIPurpose
abortYesTests for when the --abort-on-uncaught-exception flag is used.
addonsYesTests for addon functionality along with some tests that require an addon to function properly.
async-hooksYesTests for async_hooks functionality.
benchmarkNoTest 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.
commonCommon modules shared among many tests. Documentation
doctoolYesTests for the documentation generator.
es-moduleYesTest ESM module loading.
fixturesTest fixtures used in various tests throughout the test suite.
internetNoTests that make real outbound connections (mainly networking related modules). Tests for networking related modules may also be present in other directories, but those tests do not make outbound connections.
js-native-apiYesTests for Node.js-agnostic n-api functionality.
known_issuesYesTests reproducing known issues within the system. All tests inside of this directory are expected to fail consistently. If a test doesn't fail on certain platforms, those should be skipped via known_issues.status.
messageYesTests for messages that are output for various conditions (console.log, error messages etc.)
node-apiYesTests for Node.js-specific n-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 are run sequentially.
testpyTest configuration utility used by various test suites.
tick-processorNoTests 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-updatesNoTests for V8 performance integration.