Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Don't use jest --forceExit

See original GitHub issue

This is an antipattern since it can make running the test watcher less performant and the flag is meant to be a temporary solution. The best way to fix this is by passing app.callback() to supertest instead of app.listen(). The former has a server automatically created and closed by supertest, while the latter creates an unclosed server.

Issue Analytics

State:
Created 6 years ago
Comments:7 (7 by maintainers)

Top GitHub Comments

1reaction

nickmccurdycommented, Sep 19, 2017

There is no difference in how the server is requested, but the server is automatically created and closed when you use app.callback() . app.listen() does not automatically close the server, it stays open. We could set up after each statements in every test suite to manually close the servers, but I find it easier to just use app.callback(). See https://github.com/koajs/koala/pull/55/commits/31b6f42609f6c0ec20713a84a6f2ea626e9a49ae.

0reactions

nickmccurdycommented, Sep 26, 2017

Thanks! Looks like we forgot to remove the flag, see #1071.