Because the integration tests run against a real server on the Internet, it would be great to be able to run unit tests (that talk to nothing; no network, no db (or mocked db)) on their own, because they are super fast and they can be run very often (they could be hooked into the commit flow at some point).
npm test still runs all tests. Instead of calling on the other two tasks, I prefer to run all of them in the same process, so that the runner reports on all tests (instead of having two report outputs, and having to scroll up on terminal).
Because the integration tests run against a real server on the Internet, it would be great to be able to run unit tests (that talk to nothing; no network, no db (or mocked db)) on their own, because they are super fast and they can be run very often (they could be hooked into the commit flow at some point).
npm test
still runs all tests. Instead of calling on the other two tasks, I prefer to run all of them in the same process, so that the runner reports on all tests (instead of having two report outputs, and having to scroll up on terminal).