This allows the remote instance to communicate back to Selenium Wire with its requests and responses. When you create an instance of the remote webdriver, you need to specify the hostname or IP address of the machine (or container) running Selenium Wire. Selenium Wire has limited support for using the remote webdriver client. Selenium Wire also has it’s own options that can be passed in the seleniumwire_options attribute. Just instantiate the webdriver as you would normally with webdriver.Chrome() or webdriver.Firefox() passing in any desired capabilities and browser specific options for Chrome or Firefox, such as the executable path, headless mode etc. For example, to import WebDriverWait: # Sub-packages of webdriver must still be imported from `selenium` itself from import WebDriverWaitįor Chrome and Firefox you don’t need to do anything special. =webaft & t =aft & atyp =csi & ei =kgRJW7DBONKTlwTK77wQ & rt =wsrt.366,aft.58,prt.58 204 text/html charset =UTF-8Įnsure that you import webdriver from the seleniumwire package: from seleniumwire import webdriverįor sub-packages of webdriver, you should continue to import these directly from selenium. get ( '' ) # Access requests via the `requests` attribute for request in driver.
Chrome () # Go to the Google home page driver.
#BREW INSTALL CHROMEDRIVER NO AVAILABLE DRIVER#
Simple Example from seleniumwire import webdriver # Import from seleniumwire # Create a new instance of the Chrome driver driver = webdriver.