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>
36 lines
793 B
JavaScript
36 lines
793 B
JavaScript
'use strict';
|
|
|
|
require('../common');
|
|
const assert = require('assert');
|
|
const { Worker } = require('worker_threads');
|
|
|
|
{
|
|
const expectedErr = {
|
|
code: 'ERR_INVALID_ARG_TYPE',
|
|
name: 'TypeError'
|
|
};
|
|
|
|
assert.throws(() => {
|
|
new Worker(__filename, { execArgv: 'hello' });
|
|
}, expectedErr);
|
|
assert.throws(() => {
|
|
new Worker(__filename, { execArgv: 6 });
|
|
}, expectedErr);
|
|
}
|
|
|
|
{
|
|
const expectedErr = {
|
|
code: 'ERR_WORKER_INVALID_EXEC_ARGV',
|
|
name: 'Error'
|
|
};
|
|
assert.throws(() => {
|
|
new Worker(__filename, { execArgv: ['--foo'] });
|
|
}, expectedErr);
|
|
assert.throws(() => {
|
|
new Worker(__filename, { execArgv: ['--title=blah'] });
|
|
}, expectedErr);
|
|
assert.throws(() => {
|
|
new Worker(__filename, { execArgv: ['--redirect-warnings'] });
|
|
}, expectedErr);
|
|
}
|