mirror of
https://github.com/nodejs/node.git
synced 2025-05-15 11:36:57 +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>
19 lines
616 B
JavaScript
19 lines
616 B
JavaScript
'use strict';
|
|
require('../common');
|
|
const assert = require('assert');
|
|
|
|
const { kMaxLength, kStringMaxLength } = require('buffer');
|
|
const { MAX_LENGTH, MAX_STRING_LENGTH } = require('buffer').constants;
|
|
|
|
assert.strictEqual(typeof MAX_LENGTH, 'number');
|
|
assert.strictEqual(typeof MAX_STRING_LENGTH, 'number');
|
|
assert(MAX_STRING_LENGTH <= MAX_LENGTH);
|
|
assert.throws(() => ' '.repeat(MAX_STRING_LENGTH + 1),
|
|
/^RangeError: Invalid string length$/);
|
|
|
|
' '.repeat(MAX_STRING_LENGTH);
|
|
|
|
// Legacy values match:
|
|
assert.strictEqual(kMaxLength, MAX_LENGTH);
|
|
assert.strictEqual(kStringMaxLength, MAX_STRING_LENGTH);
|