Unable to run tests - Server timeout

I was trying to migrate from jest-dynamodb to dynalite but weird timeout error started appearing. I used exact same configuration from jest-dynamodb, I only updated config file name and preset. I also tried increasing jest timeout.

jest-dynalite: 3.0.0 collectCoverage: true OS: Ubuntu 16.04LTS

Coverage report is working fine.

 FAIL  test/my-test.test.js (68.543 s)
  ✕ my test (60027 ms)

  ● my test

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

      at mapper (node_modules/jest-jasmine2/build/queueRunner.js:27:45)

  ● my test

    NetworkingError: connect ECONNREFUSED 127.0.0.1:8001Error: connect ECONNREFUSED 127.0.0.1:8001



  ● my test

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

      at mapper (node_modules/jest-jasmine2/build/queueRunner.js:27:45)

(node:29000) UnhandledPromiseRejectionWarning: Error: connect ECONNREFUSED 127.0.0.1:8001
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16)
(node:29000) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:29000) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

[napsta32]

Found it. I just had to remove testEnvironment: "node", from jest.config.js.

[corollari]

I tried to reproduce your error in a repo but couldn’t, could you check this and compare that environment to your own? Are there any differences to the configuration files? If you change yoru configuration files to the ones on my repo does it work for you?

I also see that MOCK_DYNAMODB_ENDPOINT is not set.

That seems to be the cause of the problem, maybe jest is not properly picking up the preset? If that was the case I’d expect the whole thing to fail instead of getting a timeout tho, well let’s see if we can reproduce your problem first.