Connection refused after retesting. about jest-dynamodb

[freshollie]

@anothersaddeveloper I have rewritten this library to be lighter and fix this usecase, please check it out: https://github.com/freshollie/jest-dynalite

[freshollie]

It's related to this: jestjs/jest#6800

Edit: specifically this would fix it.
jestjs/jest#6800 (comment)

[Keksike]

I'm also running into this issue, and I dont have any globalSetup or globalTeardown currently. Here is my setup:

https://gist.github.com/Keksike/da2e2de048e85468f84fbc4b719b0d5c

EDIT: no idea what was causing this issue, but I switched to https://github.com/freshollie/jest-dynalite and that seems to work! Lit

[scottybrown]

I found that it's because this library uses dynamodb-local, which keeps a list of runningProcesses keyed on port.
Since this library's teardown.js calls DynamoDbLocal.stopChild rather than DynamoDbLocal.stop, runningProcesses doesn't get updated. So the next time the setup runs it thinks Dynamo is already running and doesn't start it.
Can fix it with a jest globalTeardown that runs await DynamoDbLocal.stop(8000); (or whatever port you're using), but that's making an assumption about the internals of this library which is no good.
Probably, jest-dynalite is the answer :)