The chromedriver.exe file does not exist in the current directory or in a directory on the PATH environment variable.ĭepending on your setup, it can also bomb out with : The file C:\path\to\my\project\chromedriver.exe does not exist.
But if you use Specflow/Selenium even semi-regularly, I highly recommend bookmarking this post because I’m 99% sure you will hit atleast one of these bugs when setting up a new testing project. If you are not that big into automation testing, you can probably skip this whole post. Version errors, Not finding the right exe, Nuget packages that actually include the exe but it’s the wrong version or can’t be found. And let me tell you, there are a few headaches getting this set up that I really didn’t expect. It’s the tool that actually allows you to manipulate the Google Chrome browser through selenium. A key part of using Selenium is the “ChromeWebDriver”. Seeing the browser flash infront of you and motor through tests is an amazing feeling.īut in saying that. End to end testing with Selenium is like that but on steroids. I’m one of those people that absolutely love unit tests and trying to “trick” the code with complicated scenarios. I’ve recently had the opportunity to start a Specflow/Selenium end to end testing project from scratch and my gosh it’s been fun.
0 kommentar(er)
