We really like the Xebium project and we are hoping to use Xebium for our functional testing.
All is well but we have trouble scaling up. Scaling Selenium is no problem with GRID 2 (one server and n node(s)). The unit test running manages to connect to the remote server and the test gets delegated to the node and ran perfectly. But we can’t really get Xebium work towards a Selenium hub.
In the Xebium installation there are an example suite containing the test: “Example 008 Running Tests with Selenium Server”.
Running this test generates the following error:
start browser Could not invoke constructor for StartBrowser[7]
firefox The instance decisionTable_3. does not exist on url
The instance decisionTable_3. does not exist
http://localhost The instance decisionTable_3. does not exist … and so on.
What on earth are we missing?
Environment:
- Xebium server
- Selenium GRID 2
- A Selenium Web Driver node with Firefox.
All three instances are currently on the same machine. A theory we have is that Xebium itself should be started as the server that the nodes should be registered against. But that really does not make sense.
I do not fully (or at all) understand how the Xebium server that wraps both Fitnesse and Selenium maps to the Selenium scaling architecture.
Please advice!
Best regards
@demassinner
Update:
SvaraRaderaAfter reading the source code it was a simple thing to tweak the json to call a Selnium 2 hub.
Example:
…
| script |
| start browser | { "name": "Foo bar test", "remote": "!-http://-!localhost:4444/wd/hub","platform":"ANY", "browserName":"chrome" } | on url | http://sjv.se |
| do | open | on | / |
….
Thank you for a very interesting project.