mirror of
https://github.com/nodejs/node.git
synced 2025-05-10 20:34:33 +00: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>
16 lines
375 B
JavaScript
16 lines
375 B
JavaScript
// Flags: --expose-internals
|
|
'use strict';
|
|
const common = require('../common');
|
|
const assert = require('assert');
|
|
const util = require('internal/util');
|
|
|
|
if (!process.versions.openssl) {
|
|
const expectedError = common.expectsError({
|
|
code: 'ERR_NO_CRYPTO',
|
|
type: Error
|
|
});
|
|
assert.throws(() => util.assertCrypto(), expectedError);
|
|
} else {
|
|
util.assertCrypto();
|
|
}
|