Implement driver.network_traffic for Chrome Headless Driver
Reported by
jase.wil...@gmail.com,
Jul 19 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: Use Chromedriver as a Selenium back-end. What is the expected behavior? Something like this: https://github.com/teampoltergeist/poltergeist#inspecting-network-traffic What went wrong? there is no easy way to know the network_traffic when running tests. Is it possible to expose this property as this is something we had before with the phantomJS driver poltergiest Did this work before? N/A Chrome version: 59.0.3071.115 Channel: stable OS Version: 10.0 Flash Version: Components: Internals>Headless Tests>WebDriver
,
Jul 20 2017
,
Jul 20 2017
heyo. i'm not sure what you're asking for here. the poltergeist only works with phantomjs. it doesn't work with headless chrome or chrome via selenium. network traffic is exposed in headless chrome via events from the Network domain. See https://chromedevtools.github.io/devtools-protocol/tot/Network/#events For example, Network.requestWillBeSent. You can bind together all this data with requestIds and form a full picture of the network traffic. For example: https://github.com/cyrus-and/chrome-har-capturer/tree/from-log#fromlogurl-log-options gluck!
,
Jul 20 2017
Hey Paul I didn't mean so it could work under poltergeist, I meant so it's easier to sniff network traffic when used with capybara *like* poltergeist (which does expose it) J |
|||
►
Sign in to add a comment |
|||
Comment 1 by sadrul@chromium.org
, Jul 19 2017Labels: Proj-Headless