History

Rich Trott 78520fa472 test,dgram: add tests for setBroadcast() The only tests for `setBroadcast()` (from the `dgram` module) were in `test/internet` which means they almost never get run. This adds a minimal test that can check JS-land functionality in `test/parallel`. I also expanded a comment and did some minor formatting on the existing `test/internet` test. If there were an easy and reliable way to check for the BROADCAST flag on an interface, it's possible that a version of the test could be moved to `test/sequential` or `test/parallel` once it was modified to only use internal networks. PR-URL: https://github.com/nodejs/node/pull/6750 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com>		9 years ago
..
abort	src: honor --abort_on_uncaught_exception flag	9 years ago
addons	test: favor strictEqual() in addon test	9 years ago
cctest	src: don't use locale-sensitive strcasecmp()	9 years ago
debugger	test: move test-debugger-debug-brk to sequential	9 years ago
disabled	test: abstract skip functionality to common	9 years ago
doctool	test: refactor doctool tests	9 years ago
fixtures	test: fix test-debugger-repl-term	9 years ago
gc	benchmark,test,lib: remove extra spaces	9 years ago
internet	test,dgram: add tests for setBroadcast()	9 years ago
known_issues	test: make stdout buffer test more robust	9 years ago
message	test,tools: enable linting for undefined vars	9 years ago
parallel	test,dgram: add tests for setBroadcast()	9 years ago
pummel	test: abstract skip functionality to common	9 years ago
sequential	test: move test-debugger-debug-brk to sequential	9 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: remove common.getServiceName()	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