You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could we use <ip>:<port>/json/version to retrieve the websocket url instead of relying on parsing stdout to retrieve the websocket url? The trouble with using the json endpoint is that we will need to pick and assign the port when launching the browser instance instead of allowing the browser to find an open port, which is an extra moving part in xk6-browser.
The text was updated successfully, but these errors were encountered:
Which IP and port can we connect to without knowing the WebSocket URL firsthand?
I looked into this, and we can use the --remote-debugging-address and --remote-debugging-port flags. However, once we set these to constant values, users won't be able to test with multiple k6 processes, hence the single address and port.
Could we use
<ip>:<port>/json/version
to retrieve the websocket url instead of relying on parsing stdout to retrieve the websocket url? The trouble with using the json endpoint is that we will need to pick and assign the port when launching the browser instance instead of allowing the browser to find an open port, which is an extra moving part in xk6-browser.The text was updated successfully, but these errors were encountered: