0
0
mirror of https://github.com/nodejs/node.git synced 2024-12-01 16:10:02 +01:00
nodejs/test
Geoffrey Booth 96e46d37c4
esm: replace --entry-type with --input-type
New flag is for string input only

PR-URL: https://github.com/nodejs/node/pull/27184
Reviewed-By: Jan Krems <jan.krems@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Myles Borins <myles.borins@gmail.com>
2019-04-16 12:41:59 -04:00
..
abort
addons
async-hooks
benchmark test: fix test-benchmark-module 2019-04-04 22:13:56 -07:00
cctest
code-cache src: make a Environment-independent proxy class for NativeModuleLoader 2019-04-13 17:24:51 +08:00
common
doctool
es-module esm: replace --entry-type with --input-type 2019-04-16 12:41:59 -04:00
fixtures esm: replace --entry-type with --input-type 2019-04-16 12:41:59 -04:00
internet test: fix test-dns-idna2008.js 2019-04-14 22:40:06 -07:00
js-native-api test: pass null params to napi_create_function() 2019-04-10 16:35:22 -07:00
known_issues
message process: add --unhandled-rejections flag 2019-04-15 18:29:07 +02:00
node-api
parallel esm: replace --entry-type with --input-type 2019-04-16 12:41:59 -04:00
pseudo-tty util: highlight stack frames 2019-04-15 17:30:50 +02:00
pummel test: log errors in test-fs-readfile-tostring-fail 2019-04-16 04:35:11 -04:00
report report: improve signal name validation 2019-04-10 20:36:10 -04:00
sequential lib,src,doc: add --heapsnapshot-signal CLI flag 2019-04-12 17:16:46 -04:00
testpy tools: python: ignore instead of select flake8 rules 2019-04-13 20:33:06 -04:00
tick-processor
v8-updates
wpt
.eslintrc.yaml lib: remove env: node in eslint config for lib files 2019-04-06 12:04:36 +08:00
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 successfully run on Windows, Node.js has to be checked out from GitHub 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 to function properly.
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 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-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 consistently. 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 are run sequentially.
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.