Add a serverHostname property to AbstractJasmineMojo. Useful when using...

[skrall]

... the RemoteWebDriver.

[skrall]

Just some more information on why we needed this, and why it seems like a good thing to have.

We use the selenium Remote Web Driver from Jenkins to run our tests against various browser types / versions / OSs. Without this setting, the plugin always tried to connect to localhost:, but with the remote web driver, it wouldn't be on localhost, it would be on a remote ip address. I left the default to be localhost, so it shouldn't break any existing setups.

If you need anything else, have any issues with this change - just let me know.

[klieber]

1.3.1.3 has been released already. This will need to be updated to 1.3.1.4

[klieber]

Thanks!

[tfga]

@skrall Two questions for you:

1. How did you do it?!

   I searched all over the docs (and the code!) and found nothing that would allow me to connect to a remote selenium server. I ended up implementing it myself (Ability to connect to remote Selenium server #235)

2. What strategy did you use to run the tests against different OS + browser combinations? Here's what I came up with: multiple invocations of mvn, with different profiles, e.g.:

   mvn jasmine:test -Pwindows.chrome
   mvn jasmine:test -Pwindows.firefox
   mvn jasmine:test -Pwindows.ie
   
   mvn jasmine:test -Plinux.chrome
   mvn jasmine:test -Plinux.firefox

   Did you do something different?

[skrall]

There is a Java property that selenium looks at if no URL is passed into a RemoteWebDriver. I believe it's webdriver.remote.server. So, when I ran ran maven, I was sure that property was set. java -Dwebdriver.remote.server=http://selenium:4444/wd/hub for example. There are of course other ways to set the property.

See code here.

But I do think your new property is much easier, I like it.

As for the various browsers / os, I was lucky, we only have to support one browser / version. But it's not the same version of the OS that our tests ran on. So we needed the RemoteWebDriver. But if I had to support multiple, I would do what you have done with the profiles.

[tfga]

There is a Java property that selenium looks at if no URL is passed into a RemoteWebDriver. I believe it's webdriver.remote.server.

Hum... the mystery is solved...

But I do think your new property is much easier, I like it.

:)

Thanks!

[tfga]

@skrall You might also be interested in this: #236.

[nemosx]

@tfga Did your remoteWebDriverUrl property ever make it into any searls 1.3.1.x releases? If not, did you just use the -Dwebdriver.remote.server property? Thanks in advance!

[tfga]

@nemosx

Did your remoteWebDriverUrl property ever make it into any searls 1.3.1.x releases?

No, it didn't. The project seems dead.

If not, did you just use the -Dwebdriver.remote.server property?

No, I'm using my fork. I published it internally with a different groupId and that's what we've been using.