node/test/parallel/test-stream-wrap-encoding.js
Ruben Bridgewater e038d6a1cd
test: refactor common.expectsError
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>
2019-12-31 15:54:20 +01:00

44 lines
835 B
JavaScript

// Flags: --expose-internals
'use strict';
const common = require('../common');
const StreamWrap = require('internal/js_stream_socket');
const Duplex = require('stream').Duplex;
{
const stream = new Duplex({
read() {},
write() {}
});
stream.setEncoding('ascii');
const wrap = new StreamWrap(stream);
wrap.on('error', common.expectsError({
name: 'Error',
code: 'ERR_STREAM_WRAP',
message: 'Stream has StringDecoder set or is in objectMode'
}));
stream.push('ohai');
}
{
const stream = new Duplex({
read() {},
write() {},
objectMode: true
});
const wrap = new StreamWrap(stream);
wrap.on('error', common.expectsError({
name: 'Error',
code: 'ERR_STREAM_WRAP',
message: 'Stream has StringDecoder set or is in objectMode'
}));
stream.push(new Error('foo'));
}