mirror of
https://github.com/nodejs/node.git
synced 2025-05-20 06:40:22 +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>
31 lines
646 B
JavaScript
31 lines
646 B
JavaScript
'use strict';
|
|
|
|
// Check the error condition testing for passing something other than a string
|
|
// or buffer.
|
|
|
|
const common = require('../common');
|
|
const assert = require('assert');
|
|
const zlib = require('zlib');
|
|
|
|
[
|
|
undefined,
|
|
null,
|
|
true,
|
|
false,
|
|
0,
|
|
1,
|
|
[1, 2, 3],
|
|
{ foo: 'bar' }
|
|
].forEach((input) => {
|
|
assert.throws(
|
|
() => zlib.deflateSync(input),
|
|
{
|
|
code: 'ERR_INVALID_ARG_TYPE',
|
|
name: 'TypeError',
|
|
message: 'The "buffer" argument must be of type string or an instance ' +
|
|
'of Buffer, TypedArray, DataView, or ArrayBuffer.' +
|
|
common.invalidArgTypeHelper(input)
|
|
}
|
|
);
|
|
});
|