Jonathan Samines
Jonathan Samines
> @skykanin you are right, after i got mockgoose working i realised that when i ran multiple files there was still an issue. > > With mockgoose i had to...
@JamieCorkhill that works for me
Hi @JamieCorkhill I finally got some time to take a look. After some debugging, I noticed there was an open mongodb connection, which was never closed. See a couple of...
@JamieCorkhill Yes please, await gor that one as well. I just forgot to await for it.
@cif The issue is not usually caused by `express-session` itself, but rather by the particular store used. I usually rely on the default `MemoryStore` on tests, if it is really...
@Iworb To which `host` is your server bound to? If it is different than localhost/127.0.0.1, then that is likely what is causing your issue. See https://github.com/visionmedia/supertest/issues/488#issuecomment-413094562 for more details.
@KayHS I hope the information below still is helpful. Given the way you are initializing supertest (you are providing an http server instance), it will try to get the port...
HI @Je-ni a reproduction example would be useful to determine the root of the problem.
@NBNARADHYA are you still experiencing this issue? How exactly are you using supertest?
@fakekamrankhan Both `.listen()` and `.close()` receive an optional callback, to properly wait for those operations to complete. You need to manually provide those callbacks, so that Jest waits for those...