mirror of
https://github.com/nodejs/node.git
synced 2024-12-01 16:10:02 +01:00
caee112e52
There is actually no reason to use `assert.doesNotThrow()` in the tests. If a test throws, just let the error bubble up right away instead of first catching it and then rethrowing it. PR-URL: https://github.com/nodejs/node/pull/18669 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
34 lines
613 B
JavaScript
34 lines
613 B
JavaScript
'use strict';
|
|
const common = require('../common');
|
|
if (!common.hasCrypto)
|
|
common.skip('missing crypto');
|
|
|
|
const tls = require('tls');
|
|
|
|
['foobar', 1, {}, []].forEach(function connectThrows(input) {
|
|
const opts = {
|
|
host: 'localhost',
|
|
port: common.PORT,
|
|
lookup: input
|
|
};
|
|
|
|
common.expectsError(function() {
|
|
tls.connect(opts);
|
|
}, {
|
|
code: 'ERR_INVALID_ARG_TYPE',
|
|
type: TypeError
|
|
});
|
|
});
|
|
|
|
connectDoesNotThrow(common.mustCall(() => {}));
|
|
|
|
function connectDoesNotThrow(input) {
|
|
const opts = {
|
|
host: 'localhost',
|
|
port: common.PORT,
|
|
lookup: input
|
|
};
|
|
|
|
tls.connect(opts);
|
|
}
|