Nodejs/node
1
0
Fork 0
mirror of https://github.com/nodejs/node.git synced 2024-11-21 10:59:27 +00:00
Code Issues Actions 25 Packages Projects Releases Wiki Activity
0befda6970
node/test
History
Refael Ackermann 0befda6970 tools: python: update flake8 rules 
* Tree-factor location of some *.py files for easy demarcation of
  areas to exclude.

PR-URL: https://github.com/nodejs/node/pull/25614
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
2019-04-13 20:32:55 -04:00
..
abort
addons
async-hooks
benchmark test: fix test-benchmark-module 2019-04-04 22:13:56 -07:00
cctest process: run RunBootstrapping in CreateEnvironment 2019-04-03 08:46:03 +08:00
code-cache src: make a Environment-independent proxy class for NativeModuleLoader 2019-04-13 17:24:51 +08:00
common report: add cwd to report 2019-04-02 20:48:59 -04:00
doctool
es-module
fixtures tools: python: update flake8 rules 2019-04-13 20:32:55 -04:00
internet
js-native-api test: pass null params to napi_create_function() 2019-04-10 16:35:22 -07:00
known_issues test: fix error code typo 2019-04-01 06:22:25 +02:00
message console: remove trace frame 2019-04-12 19:29:24 +08:00
node-api
parallel child_process: harden fork arguments validation 2019-04-12 08:54:13 +08:00
pseudo-tty
pummel src: implement MemoryRetainer in Environment 2019-04-04 11:09:29 +08: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
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

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.
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.