lukechilds
/
node
mirror of https://github.com/lukechilds/node.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
16823 Commits
131 Branches
446 Tags
325 MiB
 
 
 
 
 
 
Tree: c53ed73891
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'c53ed73891'
${ noResults }
node/test
heeeunkimmm c53ed73891
test: changed buffer-zero output 		7 years ago
..
abort http: assert parser.consume argument's type 7 years ago
addons test: check that this != new.target in addon 7 years ago
addons-napi tools: remove assert.fail() lint rule 7 years ago
cctest test: remove redundant `using` in cctest 7 years ago
common test: allow adding known-globals through ENV 7 years ago
debugger test: remove common.noop 7 years ago
disabled test: replace indexOf with includes and startsWith 7 years ago
doctool test: simplify test skipping 7 years ago
fixtures crypto: fix Node_SignFinal 7 years ago
gc test: reduce string concatenations 8 years ago
inspector test: remove common.fail() 7 years ago
internet test: remove common.fail() 7 years ago
known_issues test: remove invalid test 7 years ago
message test: adjust indentation for stricter linting 7 years ago
parallel test: changed buffer-zero output 7 years ago
pseudo-tty test: reduce string concatenations 8 years ago
pummel test: fix conversion of microseconds in test 7 years ago
sequential test: improve assert messages 7 years ago
testpy test: remove unused testpy code 8 years ago
tick-processor test: simplify test skipping 7 years ago
timers test: adjust indentation for stricter linting 7 years ago
.eslintrc.yaml tools: eslint - use `error` and `off` 7 years ago
README.md test: move WPT to its own testing module 8 years ago

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 direcotry, see the contributing guide.

Test Directories

Directory Runs on CI Purpose
abort No 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.
cctest Yes C++ test that is run as part of the build process.
common Common modules shared among many tests. [Documentation]
debugger No Tests for debugger functionality along with some tests that require an addon to function properly.
disabled No Tests that have been disabled from running for various reasons.
fixtures Test fixtures used in various tests throughout the test suite.
gc No Tests for garbage collection related functionality.
inspector Yes Tests for the V8 inspector integration.
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.
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.
timers No Tests for timing utilities (setTimeout and setInterval).