Provide a way to customise the port Selenium starts on

[umaar]

It would be good if we could pass some custom configuration to this.

[daaku]

Why not use the port it returns instead?

[umaar]

It's a slight limitation as there are times when customising the port can be useful, especially when running in a continuous integration environment.

[daaku]

In fact I wrote this for use this with Travis CI where a fixed port causes issues since it could be in use by another process. Does your CI environment run multiple builds in parallel?

[umaar]

The CI environment I'm looking into will eventually run multiple builds in parallel, but the intention of this issue was just to provide a way for users who wish to customise the port Selenium gets started on to do so as there are use cases where this makes sense.

[stdavis]

I would love this as well. I'm unable to get the port number after starting it so I need to be able to specify it at the beginning.

[mbrevda]

@stdavis while hardly a perfect solution, I'm getting the port number by passing it to ENV:

        seleniumRunner(function(err, selenium) {
            if (err) throw err

            process.env.SELENIUM_PORT = selenium.port
            //do something 
        })