我嘲笑了request-promise模块，除了 tslint 抱怨警告外，一切都很好。
这是我的单元测试：
import * as request from 'request-promise';
jest.mock('request-promise', () => {
return {
__esModule: true,
get: jest.fn(),
};
});
describe('csv.service.ts', () => {
it('should mock request-promise module correctly', () => {
expect(jest.isMockFunction(request.get)).toBeTruthy();
});
it('should mock get method correctly', async () => {
(request.get as jest.Mock).mockResolvedValueOnce('go?');
const actualValue = await request.get('1');
expect(actualValue).toBe('go?');
});
});
在非承诺的情况下重构这个多余的“等待”。(no-invalid-await)tslint(1)
这似乎request.get('1')是不把作为执行后承诺mockResolvedValueOnce上request.get。
更新
如果我删除async/await，第二个单元测试将失败。
FAIL src/tests/services/core/csv.service.spec.ts
csv.service.ts
✓ should mock request-promise module correctly (5ms)
✕ should mock get method correctly (9ms)
● csv.service.ts › should mock get method correctly
expect(received).toBe(expected) // Object.is equality
Expected: "go?"
Received: {}
Difference:
Comparing two different types of values. Expected string but received object.
17 |
18 | const actualValue = request.get('1');
> 19 | expect(actualValue).toBe('go?');
| ^
20 | });
21 | });
22 |
at Object.it (src/tests/services/core/csv.service.spec.ts:19:25)
Test Suites: 1 failed, 1 total
Tests: 1 failed, 1 passed, 2 total
Snapshots: 0 total
Time: 1.203s, estimated 2s
我使用类型转换来解决这个问题。因为我确定request.get('1')是Promise在执行之后mockResolvedValueOnce。
const actualValue = await (request.get('1') as PromiseLike<string>);
本文收集自互联网，转载请注明来源。
如有侵权，请联系[email protected] 删除。
我来说两句