There are two pieces of small insanity that one will experience when being a professional web developer running tests using Selenium or Chrome driver under macOS Sonoma
1/ ChromeDriver gets attached to an old version, causing the security vulnerability shown here:
session not created: This version of ChromeDriver only supports Chrome version 121
Current browser version is 119.0.6045.105 with binary path /Applications/Google Chrome for Testing.app/Contents/MacOS/Google Chrome for Testing
This small insanity seems to crop up with the way Brew installs chromedriver.
I threw away Google Chrome For Testing 119 that wouldn’t update itself.
because it made me mad that it couldn’t update itself. What kind of an app can’t update itself in 2024?
so that (throwing it away) made me happier (like Marie Kondo promised) (edited)
and then I ran
brew install chromedriver and then I did a little voodoo and then this time when I ran rspec there were….. lo-and-behold…. NO SECURITY WARNINGS.
128×27 2024-02-02 17-10-32.png
And a joyously passing test suite. So that’s my parable. Goodnight y’all!
2/ Chrome Driver for Testing cannot be explicitly allowed to be run by a third party developer, and continually shows a warning message for each and every test that is run:
The failure of the Chrome team to have a verified binary is described here, as is the fix: