I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

Hi @curtis-jotson , can you explain more which part of the code experiences time out? For example,

afterAll(() => {
    // put some logs here to see if the line reaches
    jest.useRealTimers()
})

Or

test('', async () => {
    await db.collection('test').add({ test: "I am a test document" })
    // put some logs here to see if the line reaches
})

Hello @cherylEnkidu, sorry for the delay.

This part experiences the timeout:

test('', async () => {
    await db.collection('test').add({ test: "I am a test document" })
    // put some logs here to see if the line reaches
})

when this part is uncommented:

    beforeAll(() => {
        // jest.useFakeTimers()
    })

Hi @curtis-jotson , it could be possible that faking time changes some underlining javascript and unfortunately we can only guaranteeing the performance on production environment.

It does this when connected to the online environment as well, not just the emulators. It's an issue with library halting data access when "time" isn't moving. No other data access library I've used exhibits this behaviour and it's stopping me from being able to TDD my code effectively.

Sorry for the confusion here. The team can only guarantee the performance on the production environment which including using the real time. It is possible changing the system time fails some of the security checks in the backend.

I encountered the same problem as this one. I only wanted to mock new Date(), so by providing everything except for Date, which is mentioned at https://jestjs.io/ja/docs/jest-object#jestusefaketimersfaketimersconfig, to the doNotFake option, the test started working

jest.useFakeTimers({
      doNotFake: [
        "hrtime",
        "nextTick",
        "performance",
        "queueMicrotask",
        "requestAnimationFrame",
        "cancelAnimationFrame",
        "requestIdleCallback",
        "cancelIdleCallback",
        "setImmediate",
        "clearImmediate",
        "setInterval",
        "clearInterval",
        "setTimeout",
        "clearTimeout",
      ],
      now: new Date("2022/01/01 0:00:00"),
    });

I encountered the same problem as this one. I only wanted to mock new Date(), so by providing everything except for Date, which is mentioned at https://jestjs.io/ja/docs/jest-object#jestusefaketimersfaketimersconfig, to the doNotFake option, the test started working

jest.useFakeTimers({
      doNotFake: [
        "hrtime",
        "nextTick",
        "performance",
        "queueMicrotask",
        "requestAnimationFrame",
        "cancelAnimationFrame",
        "requestIdleCallback",
        "cancelIdleCallback",
        "setImmediate",
        "clearImmediate",
        "setInterval",
        "clearInterval",
        "setTimeout",
        "clearTimeout",
      ],
      now: new Date("2022/01/01 0:00:00"),
    });

Woah thanks! I've been struggling with this for a long time!! I had to mock out Date.now() as a workaround previously.