From 84a7d52167807b89261d48085af242a7b98fc8ad Mon Sep 17 00:00:00 2001
From: Yami
selendroid-grid-plugin that contains the proxy io.selendroid.grid.SelendroidSessionProxy and a simple capability matcher io.selendroid.grid.SelendroidCapabilityMatcher.
+ %p Now you can start the Grid with the selendroid-grid-plugin. This plugin contains the proxy io.selendroid.grid.SelendroidSessionProxy as well as a simple capability matcher io.selendroid.grid.SelendroidCapabilityMatcher.
%p Command to start the server on Mac & Unix:
%pre
%code.bash
@@ -48,7 +48,7 @@ author: Dominik Dary
:escaped
java -Dfile.encoding=UTF-8 -cp "selendroid-grid-plugin-#{site.current_version}.jar;selenium-server-standalone-#{site.latest_selenium_version}.jar" org.openqa.grid.selenium.GridLauncher -capabilityMatcher io.selendroid.grid.SelendroidCapabilityMatcher -role hub -host 127.0.0.1 -port 4444
- %p Registering nodes to this grid can be done using this registration request (file name selendroid-nodes-config.json):
+ %p Registering nodes to this grid can be done using a JSON configuration file such as the following:
%pre
%code.json
= preserve do
@@ -71,8 +71,8 @@ author: Dominik Dary
"proxy": "io.selendroid.grid.SelendroidSessionProxy"
}
}
- %p This configuration describes in the section capabilities two browsers that are available on the node machine. The first one selendroid is able to run tests agains the app under test (aut) io.selendroid.testapp. The second one android can run mobile web tests. The important thing is not to mix both entries, otherwise forwarding the session to the selendroid-standalone will fail. You can find details about how capabilities are used in selendroid here.
- %p The node registration can be done by sending the node config to the hub using curl:
+ %p This configuration describes in the capabilities section two browsers that are available on the node machine. The first one, selendroid, is able to run tests agains the app under test (aut) io.selendroid.testapp. The second one, android, can run mobile web tests. The important thing is not to mix both types of test in the same entry; otherwise, forwarding the session to the selendroid-standalone will fail. You can find details about how capabilities are used in selendroid here.
+ %p The node registration can be done by sending the node config to the hub using curl (assuming the above config is named selendroid-nodes-config.json):
%pre
%code.bash
= preserve do
@@ -80,7 +80,7 @@ author: Dominik Dary
curl -H "Content-Type: application/json" -X POST --data @selendroid-nodes-config.json http://localhost:4444/grid/register
%p Now you can verify in the Selenium Grid console, that the node has been added to the grid hub.
%h2#runTests Run a Test
- %p When defining desired capabilities, please verify that they are present in the grid hub and they match to the capablities of the selendroid-standalone server. Otherwise you will get an error that the session could not be forwarded.
+ %p Before defining desired capabilities, please verify that they are present in the grid hub and they match to the capablities of the selendroid-standalone server (as discussed above). Otherwise you will get an error that the session could not be forwarded.
%pre
%code.java
= preserve do