mirror of
https://github.com/nodejs/node.git
synced 2024-11-21 21:19:50 +01: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>
21 lines
444 B
JavaScript
21 lines
444 B
JavaScript
'use strict';
|
|
|
|
const common = require('../common');
|
|
if (!common.isMainThread)
|
|
common.skip('process.chdir is not available in Workers');
|
|
const assert = require('assert');
|
|
|
|
assert.throws(
|
|
() => {
|
|
process.chdir('does-not-exist');
|
|
},
|
|
{
|
|
name: 'Error',
|
|
code: 'ENOENT',
|
|
message: /ENOENT: no such file or directory, chdir .+ -> 'does-not-exist'/,
|
|
path: process.cwd(),
|
|
syscall: 'chdir',
|
|
dest: 'does-not-exist'
|
|
}
|
|
);
|