mirror of
https://github.com/nodejs/node.git
synced 2025-05-01 08:42:45 +00:00
e038d6a1cd
This completely refactors the `expectsError` behavior: so far it's almost identical to `assert.throws(fn, object)` in case it was used with a function as first argument. It had a magical property check that allowed to verify a functions `type` in case `type` was passed used in the validation object. This pattern is now completely removed and `assert.throws()` should be used instead. The main intent for `common.expectsError()` is to verify error cases for callback based APIs. This is now more flexible by accepting all validation possibilites that `assert.throws()` accepts as well. No magical properties exist anymore. This reduces surprising behavior for developers who are not used to the Node.js core code base. This has the side effect that `common` is used significantly less frequent. PR-URL: https://github.com/nodejs/node/pull/31092 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
28 lines
670 B
JavaScript
28 lines
670 B
JavaScript
'use strict';
|
|
const common = require('../common');
|
|
const assert = require('assert');
|
|
const dgram = require('dgram');
|
|
const socket = dgram.createSocket('udp4');
|
|
|
|
socket.bind(0);
|
|
socket.on('listening', common.mustCall(() => {
|
|
const result = socket.setTTL(16);
|
|
assert.strictEqual(result, 16);
|
|
|
|
assert.throws(() => {
|
|
socket.setTTL('foo');
|
|
}, {
|
|
code: 'ERR_INVALID_ARG_TYPE',
|
|
name: 'TypeError',
|
|
message: 'The "ttl" argument must be of type number. Received type string' +
|
|
" ('foo')"
|
|
});
|
|
|
|
// TTL must be a number from > 0 to < 256
|
|
assert.throws(() => {
|
|
socket.setTTL(1000);
|
|
}, /^Error: setTTL EINVAL$/);
|
|
|
|
socket.close();
|
|
}));
|