mirrors/nodejs
mirrors/nodejs
0
0
Fork 0
mirror of https://github.com/nodejs/node.git synced 2024-12-01 16:10:02 +01:00
Code Issues Releases Activity
ab5f789e3f
nodejs/test
History
Eugene Ostroukhov ab5f789e3f inspector: enable Inspector JS API in workers 
PR-URL: https://github.com/nodejs/node/pull/22769
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: James M Snell <jasnell@gmail.com>
2018-09-17 09:49:53 -07:00
..
abort test: remove isGlibc from common 2018-08-23 16:14:44 -07:00
addons test: remove usage of deprecated V8 APIs in addons 2018-09-07 15:47:48 +02:00
addons-napi test: remove string literal message from assertion 2018-09-16 20:37:25 -07:00
async-hooks test: remove string literal message in assertions 2018-09-16 20:37:27 -07:00
cctest src: refactor Environment::GetCurrent() usage 2018-09-17 17:20:27 +02:00
code-cache
common inspector: enable Inspector JS API in workers 2018-09-17 09:49:53 -07:00
doctool tools: Include links to source code in documentation 2018-08-29 22:20:46 -04:00
es-module
fixtures tools,doc: apilinks should handle root scenarios 2018-09-09 17:48:56 -07:00
internet test: fix test-trace-events-dns 2018-09-03 11:56:22 -04:00
known_issues module: fix inconsistency between load and _findPath 2018-09-17 17:41:42 +02:00
message
parallel inspector: enable Inspector JS API in workers 2018-09-17 09:49:53 -07:00
pseudo-tty tty: make process.binding('tty_wrap') internal 2018-08-29 12:28:51 -04:00
pummel
sequential inspector: enable Inspector JS API in workers 2018-09-17 09:49:53 -07:00
testpy
tick-processor test: move common.isCPPSymbolsNotMapped to tick-processor tests 2018-08-24 11:14:07 -07:00
v8-updates test: update postmortem metadata test for V8 6.9 2018-09-07 21:08:10 +02:00
.eslintrc.yaml tools: prevent string literals in some assertions 2018-09-16 20:37:42 -07:00
README.md test,doc: adjust markdown table for linting 2018-08-12 15:30:12 -07: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.