-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
console.logs should be exposed #26
Comments
Thank you for reporting this! Because it isn't in the WebDriver spec proper, I'm hesitant to add built in support for getting console logs -- it will be too dependent on the remote end. However, for chrome at least, it is possible to get these logs using existing features without too much extra work. We can specify a data directory in the capabilities passed to chromedriver with the Here is an example that works for me:
Now running
should dump the JS log lines to stdout. Of course we don't have to print them; we could do whatever we want at that point. |
See this issue on a downstream project: quickstrom/quickstrom#64
I'm not sure if this is obtainable purely via the API as all examples I've seen claiming to support this are using some sort of language SDK. Perhaps that would be an option for us if the API doesn't support it?
i.e., quickstrom/quickstrom#64 (comment)
The text was updated successfully, but these errors were encountered: