Add example on how to run

[ojongerius]

Seeing you run jest --runInBand would have saved me some time figuring out why this did not work in my repo 😄

It might actually be worth elaborating on passing runInband, as running serially won't be great for performance.

[vladholubiev]

@ojongerius hey, thanks for the clarification!

I used --runInBand before as well, but it is not needed if you close connection properly.

See this comment from Jest team:

jestjs/jest#5571 (comment)

And a small fix which eliminated this anti-pattern: jestjs/jest@513a6fb

So what do you think if instead of mentioning --runInBand, you'd mention how to not forget to close connections?

[ojongerius]

@vladgolubev that's a good point, thanks for that suggestion. I'm running mongoose and if I add a mongoose.disconnect() in the afterAll my tests work and teardown is fast too 🎉

[ojongerius]

So AFAIC as described in #3 running with --runInBand is non optional. It could do with some explanation but as I'm not sure why this is happening I have no idea what I'd write there 😆

Any suggestions?

[vladholubiev]

@ojongerius as I replied in #3, I tested it on my repo with ~400 tests and it works without --runInBand flawlessly!