mirrors/nodejs
mirrors/nodejs
0
0
Fork 0
mirror of https://github.com/nodejs/node.git synced 2024-12-01 07:53:06 +01:00
Code Issues Releases Activity
0feb21fb02
nodejs/test
History
Shelley Vohr 0feb21fb02 src,test: add public wrapper for Environment::GetCurrent 
PR-URL: https://github.com/nodejs/node/pull/23676
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
2018-10-20 17:47:43 -04:00
..
abort
addons
addons-napi
async-hooks
cctest src,test: add public wrapper for Environment::GetCurrent 2018-10-20 17:47:43 -04:00
code-cache
common
doctool
es-module
fixtures
internet
known_issues test: fix argument order in assertion 2018-10-19 18:31:51 -07:00
message timers: run nextTicks after each immediate and timer 2018-10-17 20:38:07 -07:00
parallel tls: load NODE_EXTRA_CA_CERTS at startup 2018-10-20 09:21:16 -04:00
pseudo-tty tools,test: cleanup and dedup code 2018-10-16 11:09:53 -04:00
pummel
sequential
testpy tools,test: cleanup and dedup code 2018-10-16 11:09:53 -04:00
tick-processor
v8-updates
.eslintrc.yaml
README.md
root.status tools,test: add list of slow tests 2018-10-16 11:09:58 -04:00

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

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.
addons-napi Yes Tests for n-api functionality.
async-hooks Yes Tests for async_hooks functionality.
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.
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.)
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.