我注意到,通常在测试Node-RED中的自定义节点时不会使用Jest-我不认为有特定的原因,但这是我最熟悉的原因,因此无论如何我都在尝试。
我的测试设置看起来像
const n = require('../src/index.js');
describe('custom node', () => {
const nodeType = 'custom node';
beforeAll(done => {
helper.startServer(done);
});
afterEach(() => {
helper.unload();
});
afterAll(done => {
helper.stopServer(done);
});
it('should be loaded', () =>
new Promise((resolve, reject) => {
const flow = [{ id: 'n1', type: nodeType, name: 'test name' }];
helper.load(n, flow, () => {
const n1 = helper.getNode('n1');
try {
expect(n1).toBeTruthy();
expect(n1).toHaveProperty('name', 'test name');
resolve();
} catch (e) {
reject(e);
}
});
}));
});
并且产生的错误是
console.error node_modules/jest-jasmine2/build/jasmine/Env.js:289
Unhandled error
console.error node_modules/jest-jasmine2/build/jasmine/Env.js:290
TypeError: setTimeout(...).unref is not a function
at Immediate.<anonymous> (/dev/custom_nodes/node-red-contrib-x/node_modules/stoppable/lib/stoppable.js:43:39)
at processImmediate (internal/timers.js:439:21)
at process.topLevelDomainCallback (domain.js:126:23)
解决方案最终变得很简单:将Jest配置中的testEnvironment
设置为node
,以便setTimeout不会被Jest替换为没有unref函数的那个。
例如在jest.config.js中]
module.exports = {
testEnvironment: 'node',
};