Troubleshoot / Debug Chromedriver Issues
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # First start chromedriver from the console like this | |
| chromedriver --url-base=wd/hub --verbose | |
| # Then in another tab / window: issue a command to start a new chrome session via the JSON protocol | |
| curl -XPOST http://localhost:9515/wd/hub/session -d '{"desiredCapabilities":{"browserName":"chrome"}}' | |
| # If you can see a chrome window pop up, you're all set. If not, check the chromedriver output and fix your issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Found this via a Google search. Was useful for checking whether an issue I had was chromedriver itself or something else.