Message "Async callback was not invoked within the 5000 ms timeout specified by jest.setTimeout"

Question

I'm using Puppeteer and Jest to run some front end tests.

My tests look as follows:

describe("Profile Tab Exists and Clickable: /settings/user", () => {
    test(`Assert that you can click the profile tab`, async () => {
      await page.waitForSelector(PROFILE.TAB);
      await page.click(PROFILE.TAB);
    }, 30000);
});

Sometimes, when I run the tests, everything works as expectedly. Other times, I get an error:

Timeout - Async callback was not invoked within the 5000 ms timeout specified by jest.setTimeout.
     at node_modules/jest-jasmine2/build/queue_runner.js:68:21 <br/>
     at Timeout.callback [as _onTimeout] (node_modules/jsdom/lib/jsdom/browser/Window.js:633:19)

This is strange because:

I specified the timeout to be 30000
Whether or not I get this error is seemingly very random

Why is this happening?

@Asool Could you provide a GitHub repo? It'll be easier and faster for us to provide you with a solution. :) — Shishir Anshuman, Apr 19 '18 at 20:48
could it be that the test actually fails for the 30000ms but the error from jest simply don't include the value you passed? meaning, if you put 0ms time out, does jest error changes? — Nirit Levi, Apr 23 '18 at 12:02
I saw this error when I was debugging my tests. Stopping at a breakpoint caused to get this error — Neets, Apr 01 '19 at 10:27
this issue has surfaced again with jest v27+ see issue here: https://github.com/facebook/jest/issues/11607 — phil_lgr, Aug 15 '21 at 15:27
I am getting same error when I even import render from @testing-library/react-native. There is not resolution yet. Can anyone help in this? — Talha Arshad, Jun 08 '22 at 08:22

score 509 · Answer 1 · edited Sep 24 '20 at 13:30

509

The timeout you specify here needs to be shorter than the default timeout.

The default timeout is 5000 and the framework by default is jasmine in case of jest. You can specify the timeout inside the test by adding

jest.setTimeout(30000);

But this would be specific to the test. Or you can set up the configuration file for the framework.

Configuring Jest

// jest.config.js
module.exports = {
  // setupTestFrameworkScriptFile has been deprecated in
  // favor of setupFilesAfterEnv in jest 24
  setupFilesAfterEnv: ['./jest.setup.js']
}

// jest.setup.js
jest.setTimeout(30000)

See also these threads:

setTimeout per test #5055

Make jasmine.DEFAULT_TIMEOUT_INTERVAL configurable #652

P.S.: The misspelling setupFilesAfterEnv (i.e. setupFileAfterEnv) will also throw the same error.

edited Sep 24 '20 at 13:30

Peter Mortensen

30,738
21
105
131

answered Apr 16 '18 at 18:58

Tarun Lalwani

142,312
9
204
265

If we out `jest.setTimeOut(10000)` inside `describe` block, is it applied only to the test cases inside the `describe` block? – troglodyte07 Jun 25 '20 at 09:33
@James where exactly do you put it? Ive put in test() before the expect() and still get the timeout error... – cikatomo Sep 15 '20 at 13:56
Adding this forced my test to hang until the timeout which made me realize that my controller method wasn't calling `res.status(204).send();` only `res.status(204);` which was the source of the problem. Hope it helps – Norbert Sep 15 '20 at 23:41
1

In my case only putting `jest.setTimeOut(10000)` in `describe` helped me. Neither putting it inside test function body, nor specifying timeout as a test parameter `it.only(nm, fn, 10000)` worked. – RAM237 Mar 22 '21 at 22:40
If your promise resolves before the default timeout but you still get this error, chances are you have `jest.useFakeTimers()` somewhere in the test file (not necessarily in the same `it` block). related github issue: https://github.com/facebook/jest/issues/7151 – Erfan Azary Feb 21 '23 at 23:03

score 130 · Answer 2 · edited Feb 28 '20 at 13:47

130

It should call the async/await when it is async from test.

describe("Profile Tab Exists and Clickable: /settings/user", () => {
    test(`Assert that you can click the profile tab`, async (done) => {
        await page.waitForSelector(PROFILE.TAB);
        await page.click(PROFILE.TAB);
        done();
    }, 30000);
});

edited Feb 28 '20 at 13:47

answered Jun 26 '18 at 06:27

schrodinger's code

2,624
1
25
19

35

Why should we have `done` in an async function? Don't we simply return Promise or undefined? – Charlie Schliesser Dec 07 '18 at 19:27
5

No, this isn't correct. You don't need to call done() since you are awaiting your promises or you could just return `page.click`. done() is used, at least in my case, primarily for testing with callbacks. – Justin Apr 30 '19 at 17:29
2

Thanks guys, I have removed the `done` callback which is not needed. – schrodinger's code May 01 '19 at 03:26
33

isn't this the same code as in the original question now? – Joe May 17 '19 at 18:37
6

The presence of a parameter (named `done` in this case) in the callback causes Jest to wait until this parameter is called. Its presence is significant even if it is not used. – vaughan Jun 10 '20 at 22:05
Strange. I used `done()` to stop having this issue! – Nawaz Jun 06 '21 at 20:44

score 109 · Answer 3 · edited Sep 24 '20 at 13:41

The answer to this question has changed as Jest has evolved. Current answer (March 2019):

You can override the timeout of any individual test by adding a third parameter to the it. I.e., it('runs slow', () => {...}, 9999)

You can change the default using jest.setTimeout. To do this:

// Configuration
"setupFilesAfterEnv": [  // NOT setupFiles
    "./src/jest/defaultTimeout.js"
],

and

// File: src/jest/defaultTimeout.js
/* Global jest */
jest.setTimeout(1000)

Like others have noted, and not directly related to this, done is not necessary with the async/await approach.

e-shfiyut · Answer 4 · 2020-09-24T14:56:32.067

85

This is a relatively new update, but it is much more straight forward. If you are using Jest 24.9.0 or higher you can just add testTimeout to your config:

// in jest.config.js
module.exports = {
  testTimeout: 30000
}

edited Sep 24 '20 at 14:56

answered Dec 10 '19 at 14:53

e-shfiyut

3,538
2
30
31

To take affect, make sure to "jest --watch" again, if it is already running. – human Oct 22 '20 at 10:07
5

I wish this was the accepted answer, way more simple than having to put this config in a separate file. – Jean Paul Jan 11 '21 at 16:12
This worked like a charm, also the `jest.setTimeout` as it's own line doesn't work. – CWSites Jun 03 '21 at 19:44

score 50 · Answer 5 · edited Mar 19 '21 at 19:28

50

I would like to add (this is a bit long for a comment) that even with a timeout of 3000 my tests would still sometimes (randomly) fail with

Timeout - Async callback was not invoked within the 5000ms timeout specified by jest.setTimeout.

Thanks to Tarun's great answer, I think the shortest way to fix a lot of tests is:

describe('Puppeteer tests', () => {
  beforeEach(() => {
    jest.setTimeout(10000);
  });

  test('Best Jest test fest', async () => {
    // Blah
  });
});

edited Mar 19 '21 at 19:28

Peter Mortensen

30,738
21
105
131

answered Sep 27 '18 at 19:02

Roman

8,826
10
63
103

18

You don't need to call `jest.setTimeout()` inside `beforeEach`, calling it once is enough for all tests. – Marcos Pereira Mar 07 '19 at 11:09

score 48 · Answer 6 · edited Mar 19 '21 at 19:24

48

For Jest 24.9+, we just need to add --testTimeout on the command line:

--testTimeout= 10000 // Timeout of 10 seconds

The default timeout value is 5000 (5000 ms - 5 seconds). This will be applicable for all test cases.

Or if you want to give timeout to particular function only then you can use this syntax while declaring the test case.

test(name, fn, timeout)

Example

test('example', async () => {

}, 10000); // Timeout of 10 seconds (default is 5000 ms)

edited Mar 19 '21 at 19:24

Peter Mortensen

30,738
21
105
131

answered Nov 20 '20 at 04:54

Sharoon Ck

738
7
14

Both a space and an equal sign before the number seems like overspecification. Is it actually correct? Will it actually work as expected? (Not rhetorical questions.) – Peter Mortensen Mar 19 '21 at 19:25
1

@PeterMortensen You are right, the space is not necessary, as seen [here](https://jestjs.io/docs/cli#--testtimeoutnumber). It should instead be `--testTimeout=10000`. – Zebiano Jul 08 '21 at 22:06

score 31 · Answer 7 · edited Sep 24 '20 at 14:56

31

For Jest 24.9+, you can also set the timeout from the command line by adding --testTimeout.

Here's an excerpt from its documentation:

--testTimeout=<number>
Default timeout of a test in milliseconds. Default value: 5000.

edited Sep 24 '20 at 14:56

e-shfiyut

3,538
2
30
31

answered Oct 11 '19 at 06:41

Mr. 14

9,228
6
37
54

score 28 · Answer 8 · edited Sep 24 '20 at 13:39

28

Make sure to invoke done(); on callbacks or it simply won't pass the test.

beforeAll((done /* Call it or remove it */ ) => {
  done(); // Calling it
});

It applies to all other functions that have a done() callback.

edited Sep 24 '20 at 13:39

Peter Mortensen

30,738
21
105
131

answered Jan 27 '19 at 07:21

ZenVentzi

3,945
3
33
48

score 17 · Answer 9 · edited Mar 19 '21 at 19:19

17

Yet another solution: set the timeout in the Jest configuration file, e.g.:

{ // ... other stuff here
    "testTimeout": 90000
}

edited Mar 19 '21 at 19:19

Peter Mortensen

30,738
21
105
131

answered Aug 26 '20 at 13:11

serv-inc

35,772
9
166
188

score 9 · Answer 10 · edited Mar 19 '21 at 19:21

9

You can also get timeout errors based on silly typos. For example, this seemingly innocuous mistake:

describe('Something', () => {
  it('Should do something', () => {
    expect(1).toEqual(1)
  })

  it('Should do nothing', something_that_does_not_exist => {
    expect(1).toEqual(1)
  })
})

Produces the following error:

FAIL src/TestNothing.spec.js (5.427s)
  ● Something › Should do nothing

    Timeout - Async callback was not invoked within the 5000ms timeout specified by jest.setTimeout.
      
      at node_modules/jest-jasmine2/build/queue_runner.js:68:21
      at Timeout.callback [as _onTimeout] (node_modules/jsdom/lib/jsdom/browser/Window.js:678:19)

While the code sample posted doesn't suffer from this, it might be a cause of failures elsewhere. Also note that I'm not setting a timeout for anything anywhere - either here or in the configuration. The 5000 ms is just the default setting.

edited Mar 19 '21 at 19:21

Peter Mortensen

30,738
21
105
131

answered Nov 10 '20 at 17:17

Richard Wheeldon

973
10
25

What is the mistake? The fact that you gave the callback a parameter `something_that_does_not_exist`? – flash Jul 16 '21 at 22:49
Yes. Giving functions extra unused parameters in JavaScript is normally pointless but benign. Here it's likely to produce the above confusing error. – Richard Wheeldon Jul 18 '21 at 08:01
It Works For me, after removing done() method – Surendranath Sonawane Sep 15 '22 at 12:18

score 9 · Answer 11 · edited Mar 27 '22 at 15:21

9

Mar 14, 2022, Jest 27.5 documentation indicates a new process:

https://jestjs.io/docs/api#beforeallfn-timeout

Pass a second parameter to test with the number of msec before timeout. Works!

test('adds 1 + 2 to equal 3', () => {
    expect(3).toBe(3);
},30000);

edited Mar 27 '22 at 15:21

Jingguo Yao

7,320
6
50
63

answered Mar 15 '22 at 00:23

user2330237

1,629
5
20
39

score 7 · Answer 12 · edited Mar 19 '21 at 19:12

7

I recently ran into this issue for a different reason: I was running some tests synchronously using jest -i, and it would just timeout. For whatever reasoning, running the same tests using jest --runInBand (even though -i is meant to be an alias) doesn't time out.

edited Mar 19 '21 at 19:12

Peter Mortensen

30,738
21
105
131

answered Apr 03 '19 at 18:58

Jona

1,023
2
15
39

score 7 · Answer 13 · answered Mar 27 '22 at 15:15

test accepts a timeout argument. See https://jestjs.io/docs/api#testname-fn-timeout. Here is a sample:

async function wait(millis) {
  console.log(`sleeping for ${millis} milliseconds`);
  await new Promise(r => setTimeout(r, millis));
  console.log("woke up");
}
test('function', async () => {
  await wait(5000);
}, 70000);

score 6 · Answer 14 · edited Sep 24 '20 at 13:48

6

// In jest.setup.js
jest.setTimeout(30000)

If on Jest <= 23:

// In jest.config.js
module.exports = {
  setupTestFrameworkScriptFile: './jest.setup.js'
}

If on Jest > 23:

// In jest.config.js
module.exports = {
  setupFilesAfterEnv: ['./jest.setup.js']
}

edited Sep 24 '20 at 13:48

Peter Mortensen

30,738
21
105
131

answered Oct 31 '19 at 12:34

alexrogers

1,514
1
16
27

Doing this doesn't work, I get an error (and others on this thread) regarding "jest undefined". We shouldn't have to import `jest` on a `jest` setup file... – CWSites Jun 03 '21 at 19:42

score 5 · Answer 15 · edited Sep 24 '20 at 13:46

5

The timeout problem occurs when either the network is slow or many network calls are made using await. These scenarios exceed the default timeout, i.e., 5000 ms. To avoid the timeout error, simply increase the timeout of globals that support a timeout. A list of globals and their signature can be found here.

For Jest 24.9

edited Sep 24 '20 at 13:46

Peter Mortensen

30,738
21
105
131

answered Aug 31 '19 at 19:41

Neeraj Sewani

3,952
6
38
55

score 5 · Answer 16 · answered Nov 30 '21 at 21:25

Turns out if your expect assertions are wrong, it can sometimes spit out the exceeded timeout error message.

I was able to figure this out by putting console.log() statements in my promise callback and saw the console.log() statements were getting ran in the jest output. Once I fixed my expect assertions, the timeout error went away and tests worked.

I spent way too long to figure this out and hope this helps whoever needs to read this.

score 3 · Answer 17 · answered Jul 08 '22 at 16:40

For the jest versions greater than 27, you can add useRealTimers on the top of your spec file.

Here is the snippet

import { shortProcess, longProcess } from '../../src/index';

jest.useRealTimers();

describe(`something`, function () {
    it('should finish fine', async function () {
        await shortProcess();
        expect(1).toBe(1);
    });

    it('should fail with a timeout', async function () {
        await longProcess();
        expect(1).toBe(1);
    });

    it('should finish fine again', async function () {
        jest.setTimeout(10 * 1000);
        await longProcess();
        expect(1).toBe(1);
    }, 10000);
});

Find the github issue here on jest repository.

score 2 · Answer 18 · edited Sep 24 '20 at 13:49

2

In case someone doesn't fix the problem use methods above. I fixed mine by surrounding the async func by an arrow function. As in:

describe("Profile Tab Exists and Clickable: /settings/user", () => {
    test(`Assert that you can click the profile tab`, (() => {
      async () => {
        await page.waitForSelector(PROFILE.TAB)
        await page.click(PROFILE.TAB)
      }
    })(), 30000);
});

edited Sep 24 '20 at 13:49

Peter Mortensen

30,738
21
105
131

answered Nov 08 '19 at 16:30

suga_e

63
2

8

It seems to me that putting the arrow function around the async will not tell the test to wait for the test to complete, so while you may not get an error now, you'll have a test running outside of its thread and a) the whole test suite may complete before this test is done, not testing this code and b) future errors inside this test might show up during a different test in the suite, making your tests flaky and hard to maintain. – Mary Shaw Nov 20 '19 at 16:40

score 1 · Answer 19 · edited Mar 19 '21 at 19:17

1

In my case, this error started appearing randomly and wouldn't go away even after setting a timeout of 30000. Simply ending the process in the terminal and rerunning the tests resolved the issue for me. I have also removed the timeout and tests are still passing again.

edited Mar 19 '21 at 19:17

Peter Mortensen

30,738
21
105
131

answered Jun 05 '20 at 08:17

Saurabh Misra

491
7
14

In my case there was an error in the service and it was not running – sandeepani Mar 02 '23 at 05:32

score 1 · Answer 20 · answered Jan 13 '22 at 20:43

This probably won't be terribly helpful to most people visiting this page, but when I was getting this error it had nothing to do with Jest. One of my method calls was getting an empty object and a null exception while running locally. Once I added a null check, the failing tests and console log in question disappeared.

if(response !== null){
    this.searchSubj.next(resp);
 }
 else {
    return;
 }

score 0 · Answer 21 · edited Sep 24 '20 at 13:45

0

For those who are looking for an explanation about jest --runInBand, you can go to the documentation.

Running Puppeteer in CI environments

GitHub - smooth-code/jest-puppeteer: Run your tests using Jest & Puppeteer

edited Sep 24 '20 at 13:45

Peter Mortensen

30,738
21
105
131

answered Apr 11 '19 at 14:35

Eduardo Hernández

49
1
6

score 0 · Answer 22 · answered Sep 21 '21 at 20:30

Dropping my 2 cents here, I had the same issue on dosen of jest unit test (not all of them) and I notice that all started after I added to jestSetup this polyfill for MutuationObservers:

if (!global.MutationObserver) {
    global.MutationObserver = function MutationObserverFun(callback) {
        this.observe = function(){};
        this.disconnect = function(){};
        this.trigger = (mockedMutationsList) => {
            callback(mockedMutationsList, this);
        };
    };
}

Once I removed it test start working again correctly. Hope helps someone .

score 0 · Answer 23 · answered Mar 29 '23 at 15:37

0

modify your jest.config.X like this , X could be your language ts or js

module.exports = {
  preset: 'ts-jest',
  testEnvironment: 'node',
  //add below line to timeout//
  testTimeout: 30000
};

answered Mar 29 '23 at 15:37

Dasun wijesundara

608
6
8

score 0 · Answer 24 · answered Apr 25 '23 at 02:58

My issue was that I was using Nodejs 12 with Sequelize (pg: 7.14 - Postgres client). Then I upgraded nodejs version to 16, so "Timeout" errors showed up:

Timeout - Async callback was not invoked within the 5000 ms timeout specified by jest.setTimeout

After an hour of debugging, I found out that pg vesion 7 isn't compatible with node >= 14. Because of that, pg.connection hangs.

So my solution was: I upgrade pg version to 8

score -3 · Answer 25 · answered Sep 21 '21 at 01:17

-3

add this in your test, not much to explain

beforeEach(() => {
  jest.useFakeTimers()
  jest.setTimeout(100000)
})

afterEach(() => {
  jest.clearAllTimers()
})

answered Sep 21 '21 at 01:17

AN German

725
10
10

Message "Async callback was not invoked within the 5000 ms timeout specified by jest.setTimeout"

25 Answers25

Example

Linked