0
0
mirror of https://github.com/nodejs/node.git synced 2024-12-01 16:10:02 +01:00
nodejs/test
NickNaso 9868126546 build: expose napi_build_version variable
Expose `napi_build_version` to allow `node-gyp` to make it
available for building native addons.

Fixes: https://github.com/nodejs/node-gyp/issues/1745
Refs: https://github.com/nodejs/abi-stable-node/issues/371
PR-URL: https://github.com/nodejs/node/pull/27835
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Gabriel Schulhof <gabriel.schulhof@intel.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
2019-07-01 22:07:42 -07:00
..
abort test: add addon tests for RegisterSignalHandler() 2019-06-14 19:11:42 +02:00
addons test: skip tests related to CI failures on AIX 2019-07-02 06:41:30 +02:00
async-hooks test: do not use fixed port in async-hooks/test-httparser-reuse 2019-06-27 23:40:30 -07:00
benchmark
cctest
common tools: update eslint 2019-06-27 11:57:19 +02:00
doctool
es-module
fixtures test: reset validity dates of expired certs 2019-06-28 16:14:36 -07:00
internet lib: correct error.errno to always be numeric 2019-06-17 10:18:09 +08:00
js-native-api n-api: define ECMAScript-compliant accessors on napi_define_class 2019-06-17 12:07:08 +02:00
known_issues test: fix flaky test-vm-timeout-escape-nexttick 2019-07-02 06:49:40 +02:00
message test: skip tests related to CI failures on AIX 2019-07-02 06:41:30 +02:00
node-api test: use assert() in N-API async test 2019-06-28 04:56:34 +02:00
parallel build: expose napi_build_version variable 2019-07-01 22:07:42 -07:00
pseudo-tty test: skip tests related to CI failures on AIX 2019-07-02 06:41:30 +02:00
pummel test: switch assertion order 2019-06-25 18:15:12 +02:00
report
sequential test: skip tests related to CI failures on AIX 2019-07-02 06:41:30 +02:00
testpy
tick-processor
v8-updates
wpt
.eslintrc.yaml
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 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.