Fake Timer 不 Restored
错误信息
真实 timers 是 used 之后 fake timers 是不 restored
快速摘要
Fake timers 是启用但 从不 restored 到真实 timers, causing 时间-related issues in subsequent 测试.
为什么发生
jest.useFakeTimers() called 不使用 corresponding jest.useRealTimers().
否 afterEach Hook 到 restore 真实 timers.
Fake timers leak 到 other 测试 files.
最小示例
test('test1', () => {
jest.useFakeTimers();
// ... test logic ...
// missing jest.useRealTimers()
});
test('test2', () => {
setTimeout(() => {}, 1000); // affected by fake timers from test1
});afterEach(() => jest.useRealTimers());
test('test1', () => {
jest.useFakeTimers();
// ... test logic ...
});
test('test2', () => {
setTimeout(() => {}, 1000); // uses real timers — restored
});Restore 真实 timers in afterEach 到 prevent fake timers 从 leaking.
如何诊断
Look for jest.useFakeTimers() 不使用 jest.useRealTimers().
检查如果那里's afterEach(() => jest.useRealTimers()).
运行测试 in isolation 到 see 如果 issue 是顺序-dependent.
检查如果 setTimeout/setInterval behave unexpectedly in later 测试.
如何修复
添加 afterEach(() => jest.useRealTimers()) 到 restore 真实 timers 之后每个测试.
Or call jest.useRealTimers() at 端的 测试.
配置 Jest 使用 restoreMocks: 真 and clearTimers: 真.
如何预防
总是 restore 真实 timers in afterEach 当 using fake timers.
Or use beforeEach/afterEach pairs for fake timer 设置 and teardown.
相关资源
相关课程
- 异步测试
测试 asynchronous code.