Chrome automatically updated to \"Version 32.0.1700.72 m\" for me this morning (1/8/2014) and now all my automated tests will not run--they fail with \"System.InvalidOperati
Chrome updates happen often and not all updates will necessarily work with a particular version of chromedriver. Take control by installing the Google gpeditor admin templates and turn on the Google Chrome update policy. This way you can control and test your updates as required for both chrome and chromedriver. Note it is best to update chrome as soon as possible.
WikiHow shows you!
This is the approach I have taken since chrome 27 and chromedriver 2.1. Works well and keeps the integrity of your tests.
This is common when Chrome/Firefox updates, ChromeDriver/Selenium always need to catch up.
However, the latest ChromeDriver should support Chrome 32 already. Your situation is because you are using way out of date ChromeDriver 2.2. Please use the latest version 2.8, you can download it here.
Otherwise if you need to keep ChromeDriver 2.2, you can also downgrade your Chrome to your old version.
Just came across the same issue; And resolved by updating ChromeDriver from 2.4 to 2.8
For our project, we use npm. I resolved the same issue by removing the node_modules\chromedriver, then running:
npm install chromedriver