jest.setTimeout() is ignored if run async'ly in beforeAll() hook

[d4vidi]

🐛 Bug Report

jest.setTimeout() works if applied in a beforeAll() hook in a script specified in setupFilesAfterEnv, but does not work if applied from within or after an async execution inside beforeAll().

More illustratively, with the following code the timeout gets properly registered:

beforeAll(async () => {
  jest.setTimeout(60000);
  await doSomeInit();
});

However, replacing the two execution lines will prevent the timeout from being registered:

beforeAll(async () => {
  await doSomeInit();
  jest.setTimeout(60000);
});

Similarly, this doesn't work either:

beforeAll(async () => {
  await new Promise((resolve) => {
    jest.setTimeout(60000);
    resolve();
  });
});

i.e. you end up with the infamous Async callback was not invoked within the 5000ms timeout specified by jest.setTimeout. error message and a test failure.

To Reproduce

1. Set up a project with jest and 1 unit test that takes 6 seconds to complete.
2. Work out a config.json (i.e. jest config file) with setupFilesAfterEnv set to ["init.js"].
3. Inside init.js, specify a beforeAll() as explained above - setting the timeout to over 6 seconds.

Expected behavior

jest.setTimeout() applied in the 2 failing steps mentioned above should be registered.

Note: I initially had some thoughts about whether I should report this in light of what's already been reported in issue #6557, alongside the associated PR - #6817, but then I noticed this: Although the documentation specifying the limitations regarding jest.setTimeout() isn't entirely consistent over time, it nevertheless in no point mentions this specific use case. Rather, it limits the scope of where this should be executed (i.e. jest setup), and as for when - it only states "before the test runs", which makes this use case legitimate.

Link to repl or repo (highly encouraged)

N/A

envinfo

  System:
    OS: macOS Mojave 10.14.6
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  Binaries:
    Node: 10.15.3 - ~/.nvm/versions/node/v10.15.3/bin/node
    Yarn: 1.3.2 - /usr/local/bin/yarn
    npm: 6.13.2 - ~/.nvm/versions/node/v10.15.3/bin/npm
  npmPackages:
    jest: 24.9.x => 24.9.0

[matus-sabo]

If u specify timeout as second parameter in beforeAll function, it works as expected

beforeAll(async () => {
    // hook logic
}, 10000);

[d4vidi]

@lamanabie thanks. That only affects the timeout of the before-all clause itself, rather than applying the timeout over that and any future clauses (e.g. test()s), globally.

[VinGarcia]

I see this is an old ticket, but I am still facing the same issue, I tried the proposed solution but I still get this error:

    thrown: "Exceeded timeout of 5000 ms for a test.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

That said, even though adding the timeout as the second argument of the beforeAll() call didn't work I tried adding the timeout as the third argument of the it() function on the test that was failing, and this time it worked, i.e.:

it("should do something", async () => {
    // ...
}, 10000)

[github-actions]

This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days.

[github-actions]

This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.