This is a follow-up on 36. create a fake timer(setTimeout)

Like setTimeout, setInterval also is not accurate. (please refer Event Loop for detail).

This is OK in general web application, but might be problematic in test.

Could you implement your own setInterval() and clearInterval() to be sync? so that they have accurate timing for test. This is what FakeTimes are for.

By "accurate", it means suppose all functions cost no time, we start our function at time 0, then setInterval(func1, 100) would schedule func1 exactly at 100, 200, 300 .etc.

You need to replace Date.now() as well to provide the time.

class FakeTimer {  install() {    // replace window.setInterval, window.clearInterval, Date.now    // with your implementation  }    uninstall() {    // restore the original implementation of    // window.setInterval, window.clearInterval, Date.now  }    tick() {    // run the scheduled functions without waiting  }}

** Be careful about the infinite loops **. Your code is tested like this:

const fakeTimer = new FakeTimer()fakeTimer.install()const logs = []const log = () => {    logs.push(Date.now())}let count = 0const id = setInterval(() => {  if (count > 1) {    clearInterval(id)  } else {    log()  }  count += 1}, 100)// log 'A' at every 100, stop at 200fakeTimer.tick()fakeTimer.uninstall() expect(logs).toEqual([100,200])

Note

Only Date.now() is used when judging your code, you can ignore other time related apis.

讨论 (27)