History

Anna Henningsen 3cac616791 vm: don't print out arrow message for custom error In `AppendExceptionLine()`, which is used both by the `vm` module and the uncaught exception handler, don’t print anything to stderr when called from the `vm` module, even if the thrown object is not a native error instance. Fixes: https://github.com/nodejs/node/issues/7397 PR-URL: https://github.com/nodejs/node/pull/7398 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>		8 years ago
..
abort	test: add abort test for backtrace validation	8 years ago
addons	test: don't use internal headers in add-on tests	8 years ago
cctest	inspector: Do cleanups before notifying callback	8 years ago
debugger	test: remove non-incremental common.PORT changes	9 years ago
disabled	buffer: introduce latin1 encoding term	8 years ago
doctool	tools: make sure doctool anchors respect includes	9 years ago
fixtures	test: remove modifcation to common.PORT	9 years ago
gc	test: update weak module for gc tests	9 years ago
internet	test: remove internet/test-tls-connnect-cnnic	8 years ago
known_issues	test: add test for exec() known issue	8 years ago
message	vm: don't print out arrow message for custom error	8 years ago
parallel	net: use icu's punycode implementation	8 years ago
pseudo-tty	test: test TTY problems by fakeing a TTY using openpty	9 years ago
pummel	test: abstract skip functionality to common	9 years ago
sequential	test: use common.fixturesDir almost everywhere	8 years ago
testpy	test: fix default value for additional param	9 years ago
timers	benchmark,test,lib: remove extra spaces	9 years ago
.eslintrc	test,tools: limit lint tolerance of gc global	9 years ago
README.md	test: fix another flaky stringbytes test	9 years ago
common.js	test,win: skip addons/load-long-path on WOW64	9 years ago

README.md

Tests

abort

Tests for when the --abort-on-uncaught-exception flag is used.

Runs on CI
No

addons

Tests for addon functionality along with some tests that require an addon to function properly.

Runs on CI
Yes

cctest

C++ test that is run as part of the build process.

Runs on CI
Yes

debugger

Tests for debugger functionality.

Runs on CI
No

disabled

Tests that have been disabled from running for various reasons.

Runs on CI
No

fixtures

Test fixtures used in various tests throughout the test suite.

gc

Tests for garbage collection related functionality.

Runs on CI
No

internet

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.

Runs on CI
No

known_issues

Tests reproducing known issues within the system.

Runs on CI
No

message

Tests for messages that are output for various conditions (console.log, error messages etc.)

Runs on CI
Yes

parallel

Various tests that are able to be run in parallel.

Runs on CI
Yes

pummel

Various tests for various modules / system functionality operating under load.

Runs on CI
No

sequential

Various tests that are run sequentially.

Runs on CI
Yes

testpy

Test configuration utility used by various test suites.

timers

Tests for timing utilities (setTimeout and setInterval).

Runs on CI
No