Parse capabilities from console

[nipafx]

In the course of setting up end-to-end tests for my application, I wanted to dynamically determine how many grid nodes there are, so I can run each test once for each node. Since there is no endpoint exposing that information, I ended up parsing the output of /grid/console. See SeleniumGrid::parseCapabilities in this snippet (needs tests and documentation!).

Would you be interested to include that functionality?

[krmahadevan]

@nicolaiparlog - Thanks for reaching out. Yes we can include that for sure in the library.
Oh btw, in case you weren't aware, I worked on adding some rest end-points to the actual grid itself as part of these two PRs

1. Enriching Hub Status to include Node info SeleniumHQ/selenium#6127 to include node information.

So now you could do something like GET on http://localhost:4444/grid/api/hub/status?configuration=nodes and you would receive a JSON payload such as

{
  "nodes": [
    {
      "browsers": [
        {
          "browser": "safari",
          "slots": {
            "busy": 0,
            "total": 1
          }
        },
        {
          "browser": "chrome",
          "slots": {
            "busy": 0,
            "total": 5
          }
        },
        {
          "browser": "firefox",
          "slots": {
            "busy": 1,
            "total": 5
          }
        }
      ],
      "id": "http://192.168.1.6:23375"
    }
  ],
  "success": true
}

2. A Hub API that can query all running sessions. SeleniumHQ/selenium#6158 to get session information from all nodes.

So now you could do something like GET on http://localhost:4444/grid/api/sessions and you would receive a JSON payload such as

{
  "proxies": [
    {
      "id": "http://192.168.1.6:23375",
      "remoteHost": "http://192.168.1.6:23375",
      "sessions": {
        "status": 0,
        "value": [
          {
            "id": "a0cf95c1-446f-6749-afdd-b446546a9714",
            "capabilities": {
              "acceptInsecureCerts": false,
              "browserName": "firefox",
              "browserVersion": "61.0.1",
              "moz:accessibilityChecks": false,
              "moz:headless": false,
              "moz:processID": 47184,
              "moz:profile": "/var/folders/mj/81r6v7nn5lqgqgtfl18spfpw0000gn/T/rust_mozprofile.LHpIaGzYWGwZ",
              "moz:useNonSpecCompliantPointerOrigin": false,
              "moz:webdriverClick": true,
              "pageLoadStrategy": "normal",
              "platformName": "darwin",
              "platformVersion": "17.7.0",
              "rotatable": false,
              "timeouts": {
                "implicit": 0,
                "pageLoad": 300000,
                "script": 30000
              }
            }
          }
        ]
      }
    }
  ],
  "success": true
}

Both these PRs are now part of Selenium 3.14

I have been planning on including support for both these end-points over the weekend.

So let me know if you prefer this newer way of getting that information.

[nipafx]

Argh, that would've been much better and more stable than parsing the HTML. 🤣

Although, on my grid (running the selenium/hub:3.14.0-arsenic docker image) http://localhost:4444/grid/api/sessions returns this:

{
    "proxies": [],
    "success": true
}

(I remember trying that one out.)

[krmahadevan]

For the /api/sessions to work, you need to have atleast one active session running. Can you please quickly check that ?

[nipafx]

I started using Selenium only yesterday, so I'm still a noob. 😊 What's a session and how do I get one?

[krmahadevan]

You just need to point to the grid and try instantiating a new RemoteWebDriver [ This is usually how you run a test case pointing to the grid ] Something like this: https://github.com/RationaleEmotions/talk2grid/blob/master/src/test/java/com/rationaleemotions/GridApiAssistantTest.java#L37-L58

…

[nipafx]

Yes, that works and the proxies show up one after another (the tests don't run in parallel). But then I can't use that endpoint to create tests, so I'm limited to http://localhost:4444/grid/api/hub/status?configuration=nodes.

[krmahadevan]

The end-point http://localhost:4444/grid/api/sessions is not meant to create tests. Its only intended to introspect into a grid and find out what tests are currently running in the hub.

…