Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

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

See original GitHub issue

Hello guy,

Please help on this issue that I have no idea to solve this problem.

Do you want to request a feature or report a bug? bug

What is the current behavior?

 Timeout - Async callback was not invoked within the 5000ms timeout specified by jest.setTimeout.
      at ../../../../Users/chhoeurng.sakona/AppData/Roaming/npm/node_modules/jest-cli/node_modules/jest-jasmine2/build/queue_runner.js:68:21

My current code

it ('GET should return a status of 200 OK', function (done) {
        frisby
            .get('url-api')
            .expect('status', 200)
            .done(done);
    });

What is the current behavior? It should work normally and no error.

Please provide your exact Jest configuration I do not have configuration

Run npx envinfo --preset jest in your project directory and paste the results here

 System:
    OS: Windows 10
    CPU: x64 Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
  Binaries:
    Node: 8.11.1
    Yarn: Not Found
    npm: 5.6.0
   jest v22.4.3

Issue Analytics

State:
Created 5 years ago
Comments:5

Top GitHub Comments

2reactions

ross2411commented, Apr 13, 2018

sorry, apologises. I thought this was the issue tracker for Frisby!! 😳

0reactions

github-actions[bot]commented, May 12, 2021

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.

Top Results From Across the Web

Message "Async callback was not invoked within the 5000 ms ...

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...

Async callback was not invoked within the 5000ms timeout not ...

For anyone experiencing the same issue with jest puppeteer tests, I found a workaround to make the failure message display the line where...

Async callback was not invoked within the 5000ms timeout ...

I have problem with api-testing with jest. What is the current behavior? Timeout - Async callback was not invoked within the 5000ms timeout...

Timeout error within 5000ms - Node - Code with Mosh Forum

I get this error message that says: : Timeout - Async callback was not invoked within the 5000 ms timeout specified by jest.setTimeout....

async callback was not invoked within the ... - Code Grepper

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