Make tunnel usage optional

[aik099]

Right now the Selenium2 driver factory always sets tunnel-identifier desired capability (see https://github.com/Behat/MinkExtension/blob/master/src/Behat/MinkExtension/ServiceContainer/Driver/Selenium2Factory.php#L63-L68) whenever it encounters TRAVIS_JOB_NUMBER environment variable (= every test that runs on Travis CI).

I see 2 problems with that:

• it's Sauce Labs specific desired capability name and other Selenium servers (e.g. standard one or BrowserStack) won't benefit from it's presence
• user is forced to establish a Sauce Labs tunnel, because otherwise the connection won't be established due usage of non-existing tunnel

[tikohatico]

Very actuall issue, currently I can't run test from Jenkins
Do we know any solution of adding tunnel-identifier or how to use shared tunel from jankins but not specific?
Regards

[aik099]

No way currently. I'm not sure how this can be changed without doing a BC break.

You're welcome to send a PR.

[OGProgrammer]

Had this issue, put a pr up #287