0
0
mirror of https://github.com/nodejs/node.git synced 2024-11-30 07:27:22 +01:00
nodejs/test
Weijia Wang 9e0f771224 buffer: improve error messages
Some errors in buffer module losed some arguments or received
wrong arguments when they were created. This PR added these
losing arguments and fixed the wrong arguments.

PR-URL: https://github.com/nodejs/node/pull/14975
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
2017-08-24 14:49:47 -07:00
..
abort
addons test: extend async addon test 2017-08-24 21:01:36 +02:00
addons-napi test: remove unused parameters 2017-08-23 08:17:01 -07:00
async-hooks test: fix async-hooks tests 2017-08-24 10:56:24 -04:00
cctest src: Node implementation of v8::Platform 2017-08-17 20:26:55 +02:00
common test, win: fix IPv6 detection on Windows 2017-08-24 15:56:04 +02:00
debugger
doctool
fixtures test: do not modify fixtures in test-fs-chmod 2017-08-23 10:55:55 -07:00
gc
inspector test: Mark test-stop-profile-after-done flaky 2017-08-17 14:40:22 -07:00
internet dns: add verbatim option to dns.lookup() 2017-08-23 14:53:47 -07:00
known_issues test: add known issue for vm module 2017-08-23 12:16:57 -07:00
message lib: instantiate console methods eagerly 2017-08-23 11:41:15 -07:00
parallel buffer: improve error messages 2017-08-24 14:49:47 -07:00
pseudo-tty
pummel
sequential test: make timers-blocking-callback more reliable 2017-08-20 15:41:18 -07:00
testpy
tick-processor fix --prof-process --preprocess flag 2017-08-23 08:19:14 -07:00
timers
.eslintrc.yaml
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 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 debuggerfunctionality along with some tests that require an addon to function properly.
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.
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).