¿Dónde puedo encontrar un esquema o documentación para la configuración del concentrador de red Se 2 json?

Question

Tengo un concentrador de red Se 2 ejecutándose. ¿Dónde puedo encontrar documentación para los efectos y el esquema del parámetro -hubConfig? Actualmente mi hub de red muestra: "updated with grid2 config : No hub config file specified. To specify one, use -hubConfig XXX.json where XXX.json is a hub config file". Puedo usar el hub sin esta configuración.

He encontrado ejemplos en blogs y problemas, pero no hay documentación clara.

blogs: http://opensourcetester.co.uk/2011/07/06/selenium-grid-2/

cuestiones: http://code.google.com/p/selenium/issues/detail?id=2399

Answer 1

que he encontrado un buen punto de partida está mirando examples in the Selenium Grid 2 code base.

Aquí es un archivo de cubo de muestra (suponemos que nombramos el archivo hub.json JSON):

Uso: java-jar selenio-server-standalone-2.6.0.jar concentrador hub -role -hubConfig. JSON

{ 
    "host": null, 
    "port": 4444, 
    "newSessionWaitTimeout": -1, 
    "servlets" : [], 
    "prioritizer": null, 
    "capabilityMatcher": "org.openqa.grid.internal.utils.DefaultCapabilityMatcher", 
    "throwOnCapabilityNotPresent": true, 
    "nodePolling": 5000, 

    "cleanUpCycle": 5000, 
    "timeout": 300000, 
    "maxSession": 5 
} 

aquí es un archivo de nodo muestra (asumir el archivo se llama rc.json):

uso: java-jar selenio-server-standalone-2.6.0.jar -role rc -nodeConfig rc.json

{ 
    "capabilities": 
     [ 
     { 
      "browserName": "firefox", 
      "maxInstances": 5 
     }, 
     { 
      "browserName": "chrome", 
      "maxInstances": 5 
     }, 
     { 
      "browserName": "internet explorer", 
      "maxInstances": 1 
     } 
     ], 
    "configuration": 
     { 
     "nodeTimeout":120, 
     "port":5555, 

     "hubPort":4444, 
     "hubHost":"localhost", 

     "nodePolling":2000, 

     "registerCycle":10000, 
     "register":true, 
     "cleanUpCycle":2000, 
     "timeout":30000, 
     "maxSession":5, 
     } 
} 

Puede crear el uso del formato similar para la función "wd" si se requiere una configuración diferente.

Answer 2

Los documentos de wiki son escasos, pero hay muchos comentarios útiles en la fuente. GridHubConfiguration.java es donde debería comenzar. He aquí una muestra:

/** 
    * how often in ms each proxy will detect that a session has timed out. All new proxy registering 
    * will have that value if they don't specifically mention the parameter. 
    */ 
    private int cleanupCycle; 

    /** 
    * how long a new session request can stay in the queue without being assigned before being 
    * rejected. -1 = forever. 
    */ 
    private int newSessionWaitTimeout; 

I estaba buscando lo que significaba la timeout config, found here:

/** 
    * how many ms can a session be idle before being considered timed out. Working together with 
    * cleanup cycle. Worst case scenario, a session can be idle for timeout + cleanup cycle before the 
    * timeout is detected. 
    */ 
    public static final JsonKey CLIENT_TIMEOUT = JsonKey.key("timeout"); 

Answer 3

Los javadocs y varios sourcecode archivos son útiles hasta cierto punto, pero la wiki no es muy útil y los diversos ejemplos de configuración parecen inconsistentes hasta que profundices en el código. Por ejemplo, DefaultHub.json especifica "timeout" : 300000, lo que lleva a uno a suponer que el tiempo de espera está en ms, pero si observa ejemplos de línea de comandos, verá que el tiempo de espera se especifica en segundos. Si observa el código, verá que, de hecho, el esquema de configuración JSON tiene tiempo de espera (y todos los demás valores de tiempo) en ms, pero todos los demás esquemas de configuración toman el tiempo de espera (y algunos otros valores de tiempo) en segundos.

La documentación más legible y concisa que he encontrado para las opciones de concentrador y nodo está en una copia anterior de GridParameters.properties (que ya no parece existir), pero tenga en cuenta que valores de tiempo en un archivo de configuración JSON están en ms:

role = <hub|node> (default is no grid, just run an RC/webdriver server). When launching a node, the parameters will be forwarded to the server on the node, so you can use something like -role node -trustAllSSLCertificates. In that case, the SeleniumServer will be launch with the trustallSSLCertificates option. 

# hub config 
host = (hub & node) <IP | hostname> : usually not needed and determined automatically. For exotic network configuration, network with VPN, specifying the host might be necessary. 
port = (hub & node) <xxxx> : the port the remote/hub will listen on. Default to 4444. 


throwOnCapabilityNotPresent = (hub) <true | false> default to true. If true, the hub will reject test requests right away if no proxy is currently registered that can host that capability.Set it to false to have the request queued until a node supporting the capability is added to the grid. 
newSessionWaitTimeout = (hub) <XXXX>. Default to no timeout (-1) the time in ms after which a new test waiting for a node to become available will time out.When that happens, the test will throw an exception before starting a browser. 

capabilityMatcher = (hub) a class implementing the CapabilityMatcher interface. Defaults to org.openqa.grid.internal.utils.DefaultCapabilityMatcher. Specify the logic the hub will follow to define if a request can be assigned to a node.Change this class if you want to have the matching process use regular expression instead of exact match for the version of the browser for instance. All the nodes of a grid instance will use the same matcher, defined by the registry. 
prioritizer = (hub) a class implementing the Prioritizer interface. Default to null (no priority = FIFO).Specify a custom prioritizer if you need the grid to process the tests from the CI, or the IE tests first for instance. 
servlets = (hub & node) <com.mycompany.MyServlet,com.mycompany.MyServlet2> to register a new servlet on the hub/node. The servlet will accessible under the path /grid/admin/MyServlet /grid/admin/MyServlet2 


grid1Yml = (hub) a YML file following grid1 format. 
hubConfig = (hub) a JSON file following grid2 format that defines the hub properties. 
nodeConfig = (node) a JSON file following grid2 format that defines the node properties. 


# config that will be inherited by the proxy and used for the node management. 
cleanupCycle = (node) <XXXX> in ms. How often a proxy will check for timed out thread. 
timeout = (node) <XXXX> the timeout in seconds before the hub automatically ends a test that hasn't had any activity in the last X seconds. The browser will be released for another test to use. This typically takes care of the client crashes. 
browserTimeout= (hub/node) The timeout in seconds a browser can hang 
hub = (node) <http://localhost:4444/grid/register> : the url that will be used to post the registration request. This option takes precedence over -hubHost and -hubPort options. 
hubHost = (node) <IP | hostname> : the host address of a hub the registration request should be sent to. Default to localhost. Option -hub takes precedence over this option. 
hubPort = (node) <xxxx> : the port listened by a hub the registration request should be sent to. Default to 4444. Option -hub takes precedence over this option. 
proxy = (node) the class that will be used to represent the node. By default org.openqa.grid.selenium.proxy.DefaultRemoteProxy. 
maxSession = (node) max number of tests that can run at the same time on the node, independently of the browser used. 
registerCycle = (node) how often in ms the node will try to register itself again.Allow to restart the hub without having to restart the nodes. 
nodePolling = (node) in ms. Interval between alive checks of node how often the hub checks if the node is still alive. 
unregisterIfStillDownAfter = (node) in ms. If the node remains down for more than unregisterIfStillDownAfter millisec, it will disappear from the hub.Default is 1min. 
downPollingLimit = (node) node is marked as down after downPollingLimit alive checks. 
nodeStatusCheckTimeout = (node) in ms. Connection and socket timeout which is used for node alive check.