One thing I realise I didn't explain - there is no way to test separate configurations without restarting node (due to the various require imports and the fact that node sets up stuff to do with the config at the time that require is loaded). So if we want to test more than one  configuration file, we can't without the two runs.

The other advantage of the two runs (which is why I did it this way), is that we'll be running the tests in both development and production modes. As node itself changes things slightly, and we do the same (e.g. debug), this might help us to detect any issues of development versus production.

I'll admit this could cause problems with the local environment later on, however, we've generally been ignoring the WSURL in tests, so unless we add something else that's environment dependent, I'm not sure we'll have too much of an issue.

Note that the patch is also set up to ignore the local.json to stop folk's local config getting in the way.