mirror of https://github.com/nodejs/node.git synced 2024-12-01 16:10:02 +01:00

History

Ruben Bridgewater 78aa348f4e test: refactor all benchmark tests to use the new test option PR-URL: https://github.com/nodejs/node/pull/31396 Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>		2020-02-09 13:31:54 +01:00
..
abort
addons
async-hooks	test: mark additional tests as flaky on Windows	2020-02-01 22:58:56 +01:00
benchmark	test: refactor all benchmark tests to use the new test option	2020-02-09 13:31:54 +01:00
cctest	test: unset NODE_OPTIONS for cctest	2020-02-03 12:11:06 -08:00
common	benchmark: add `test` and `all` options and improve errors	2020-02-09 13:31:45 +01:00
doctool
es-module	esm: import.meta.resolve with nodejs: builtins	2020-02-03 18:31:02 +02:00
fixtures	esm: import.meta.resolve with nodejs: builtins	2020-02-03 18:31:02 +02:00
internet
js-native-api	test: cover property n-api null cases	2020-01-25 21:23:05 -08:00
known_issues
message
node-api	n-api: free instance data as reference	2020-02-06 12:43:24 -08:00
parallel	stream: finished callback for closed streams	2020-02-08 23:34:40 +01:00
pseudo-tty	src,lib: make ^C print a JS stack trace	2020-01-28 13:52:27 +08:00
pummel	worker: add ability to take heap snapshot from parent thread	2020-02-03 07:04:13 -08:00
report	test: verify threadId in reports	2020-01-31 19:15:46 -08:00
sequential	worker: add ability to take heap snapshot from parent thread	2020-02-03 07:04:13 -08:00
testpy
tick-processor
tools
v8-updates
wasi
wpt
.eslintrc.yaml
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 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.