All tests timeout on fresh API generation on Windows 10.

On a fresh generation of the REST API on Windows 10 all the tests timeout with errors similar to this:
```
FAIL src\services\response\index.test.js (16.109s)
● success › responds with passed object and status 200

Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.

at Timeout._onTimeout (node_modules\jest-jasmine2\vendor\jasmine-2.5.2.js:1979:23)
at ontimeout (timers.js:365:14)
at tryOnTimeout (timers.js:237:5)
at Timer.listOnTimeout (timers.js:207:5)
```

I've tried to get the exact packages version listed in the npm package (instead of the most recent ones) but nothing changed. I've also tried on differend windows machines (both Windows 10 and 7) without success. Node and mongo are updated to latest versions.

I haven't found anyone else with this issue so far and it seems strange. What can be the problem?

It might be partially mockgoose related since removing the mock and using a real database makes the firsts tests pass but then, after an handful of passed tests, all the following cases timeout.

Any idea?

Reproduce the fresh REST API generation on Windows 10 and start with src\services\response\index.test.js. Compare the generated setup using mockgoose with the real database behavior and inspect the installed package versions. Done means the generated test suite no longer times out on the affected Windows environments.

Written by the indexing model from the issue text.