mirrors/nodejs
mirrors/nodejs
0
0
Fork 0
mirror of https://github.com/nodejs/node.git synced 2024-11-29 23:16:30 +01:00
Code Issues Releases Activity
a4e46df87f
nodejs/test
History
Matthew Cantelon 201ecef767
test: include actual value in assertion message 
PR-URL: https://github.com/nodejs/node/pull/15935
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
2017-10-29 09:34:26 +01:00
..
abort
addons test: use common.buildType in repl-domain-abort 2017-10-27 09:50:37 -07:00
addons-napi test: include actual value in assertion message 2017-10-29 09:34:26 +01:00
async-hooks
cctest test: allow tests to pass without internet 2017-10-26 07:57:43 +02:00
common test: use process.features.debug in common module 2017-10-27 10:04:23 -07:00
doctool
es-module module: fix hook module CJS dependency loading 2017-10-28 13:22:55 +02:00
fixtures module: fix hook module CJS dependency loading 2017-10-28 13:22:55 +02:00
gc
internet test: show values instead of assertion message 2017-10-28 22:18:02 +02:00
known_issues test: add failing vm tests to known_issues 2017-10-27 10:27:14 +02:00
message timers: cleanup extraneous property on Immediates 2017-10-23 11:02:53 +02:00
parallel test: replace fixturesDir in test-tls-connect 2017-10-28 19:08:56 -07:00
pseudo-tty tty,doc: add type-check to isatty 2017-10-22 16:51:10 -07:00
pummel
sequential crypto: migrate timingSafeEqual to internal/errors 2017-10-26 07:47:16 -07:00
testpy
tick-processor
timers
.eslintrc.yaml
README.md

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.

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.
cctest Yes C++ test that is run as part of the build process.
common Common modules shared among many tests. Documentation
es-module Yes Test ESM module loading.
fixtures Test fixtures used in various tests throughout the test suite.
gc No Tests for garbage collection related functionality.
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.
timers No Tests for timing utilities (setTimeout and setInterval).

When a new test directory is added, make sure to update the CI_JS_SUITES variable in the Makefile and the js_test_suites variable in vcbuild.bat.