Don't try to run PhantomJS if there's already something running at the same port

[igorsantos07]

Given #20, we end up by having PhantomJS running all the time. That's not as bad, after all. However, if you try to run tests a second time, it hangs when trying to turn PhantomJS on.
Maybe it could skip running PhantomJS when the port is being used?

[grantlucas]

Though Phantoman could be set up to automatically detect an open port, I'm not sure if it would work with WebDriver. The issue is that the WebDriver module and Phantoman need to be set to the same port and I don't think Phantoman could alter WebDriver's settings.

It would be neat to have the open port detection in there but due to the nature of these extensions, I don't think it will be possible.

We use Phantoman in our automated tests in parallel by using a script we wrote to alter the Codeception configuration. So what it does is look for an open available port using PHP Port Finder between a certain range and then alters the Yaml config files to use the new port number for both WebDriver and Phantoman.

Something like that may be overkill for your setup and I'm really hoping #20 will fix all of this.

[igorsantos07]

Indeed that seems overkill.
However, I didn't meant to detect an available port :)
I think the project could skip running/killing (and maybe print a warning) if the given port is occupied. This way if you already have phantomjs running (given other reasons) there's no need to alter CodeCeption settings to run the tests.
Without that, if we have another phantom running on the same port the tests will fail to run.

[grantlucas]

Ah true. Alright, that would be possible! I'll look into getting that added.