Issue metadata
Sign in to add a comment
|
'Debug' is no longer a valid category in console logs - cannot scrape debug logs in automated tests
Reported by
nathanie...@am.sony.com,
Apr 18 2018
|
||||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.106 Safari/537.36
Steps to reproduce the problem:
1. In selenium-webdriver, run a test that sends an info, warning and debug log to the console
2. Then, print out browser.log('browser')
What is the expected behavior?
All three logs will be printed in the console capture.
What went wrong?
The debug log does not appear in the console output. Only the warning and info logs appear.
Did this work before? Yes Chrome 64
Chrome version: 66.0.3359.106 Channel: stable
OS Version: OS X 10.12.6
Flash Version:
I am part of a QA department that uses automated testing to monitor regressions in our software. It looks like the 'debug' log category is no longer used in the Chrome developer console as of version 65. With no console log level, we can't capture those debug logs in our automated tests. This is a serious problem for us because our automated tests rely on those debug logs to be sure our applications are speaking to our analytics software. Our tests pass on Chrome 64 and below and fail on Chrome 65 and up.
,
Apr 18 2018
John, do you know what's going on here?
,
Apr 19 2018
The "debug" level was removed from ChromeDriver by https://crrev.com/528710. Description for that CL claims that "debug" level is no longer used. But looks like we're still receiving logs at that level. Lei: Do you know what's going on?
,
Apr 19 2018
nathaniel.cohn@ Thanks for the issue. Adding 'TE-NeedsTriageHelp' label for further help in triaging the issue, as this is related to selenium-webdriver. Thanks..
,
Apr 19 2018
,
Apr 19 2018
johnchen: I have no idea what's going on. If you look in my CL, you can see I was just cleaning up someone else's old TODO. Since you approved my CL, and you approved r469104 which added the TODO in the first place, I thought everything was going according to plan.
,
Apr 19 2018
Mac triage: assigning to johnchen@ per #6.
,
Apr 26 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/b1ccf2b1483b97c8890362ff94fabdba373a3e0c commit b1ccf2b1483b97c8890362ff94fabdba373a3e0c Author: John Chen <johnchen@chromium.org> Date: Thu Apr 26 20:37:47 2018 [ChromeDriver] Add console logging levels This reverts part of https://crrev.com/c/528710, to add back "debug" as a valid console logging level. The "debug" level was originally removed because it has been replaced by "verbose" in Log.Log.entryAdded events. However, it is still used in Runtime.consoleAPICalled events. Also added "timeEnd" level that is used by Runtime.consoleAPICalled. Bug: 834310 Change-Id: Ia19ac9fd1223b4cb4e73e93779f20e7f151c8bb8 Reviewed-on: https://chromium-review.googlesource.com/1026376 Reviewed-by: Jonathon Kereliuk <kereliuk@chromium.org> Commit-Queue: John Chen <johnchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#554127} [modify] https://crrev.com/b1ccf2b1483b97c8890362ff94fabdba373a3e0c/chrome/test/chromedriver/chrome/console_logger.cc
,
Apr 30 2018
Fix checked in, and will be part of upcoming ChromeDriver 2.39. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by vamshi.kommuri@chromium.org
, Apr 18 2018