adorableio/codename-gozer — pull request #4 by rylnd (2014-08-07 17:01:20+00:00)
Title: Gozerify

@itsthatguy

I moved a bunch of stuff around. Gozer is now the phantom 'driver', and our phantom wrapper is just a wrapper.

I've got it so that the tests fail better when the server isn't running, but they're still not running the server themselves. Things I'm thinking about, in regard to that:
* Running the server requires managing two things: the PID and the port
* passing a 'run server' command to Gozer would solve the 'which port' part (you can specify which port in the command), but I don't know how Gozer would know to kill the server at the end.
* If we did the above, I guess it could manage a pidfile, and then we provide some 'kill server' hook that you call in the afterAll hook of your tests?
* Or, if we spawn that server process through the tests, can the server be auto-killed when the test process is done? [Maybe?](http://stackoverflow.com/questions/284325/how-to-make-child-process-die-after-parent-exits)