Jamie Corkhill

Were any other solutions found for this issue? I have a similar problem. When I run my test suite normally, I get the warning that Jest did not exit one...

More detailed information for my above comment can be found in this SO question: https://stackoverflow.com/questions/56027190/jest-memory-leak-testing-express-middleware

@lucianonooijen @danielantelo @marcospgp Did you ever find a solution other than `--forceExit` and the solution provided above? Thanks.

@jonathansamines I did try solution proposed in the comment you linked to, but I recieve the same response: ``` node_modules/env-cmd/bin/env-cmd.js config/test.env node_modules/jest/bin/jest.js auth.test.js PASS __tests__/middleware/auth.test.js Express Auth Middleware √ Should...

@jonathansamines Great. Thanks for your time. I'll start building it now, and you'll be able to run the server as an `npm` script with environment variables pre-loaded.

@jonathansamines Alright. Repro complete. Please bear with me if this does not suit your needs. It is my first time creating an isolated reproduction example. The only script you can...

@jonathansamines Sorry for the late response. I did merge your changes and take a brief look, but I've been busy lately and have not yet had a chance to test...

@jonathansamines I just tested your changes and it worked fantastically without memory leaks. I did have one question, though. In `auth.test.js`, in the `beforeAll` hook, you have this: ```javascript //...

@jonathansamines Thank you.

@jonathansamines And I just wanted to make sure you know that I really appreciate your help and time. I have many test suites, and they've been taking a long time...