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:
Selenium::WebDriver::Error::SessionNotCreatedError:
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.
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:

Run brew install chromedriver to update chrome driver, then
run xattr -d com.apple.quarantine /opt/homebrew/bin/chromedriver
It’s hard tto find well-informed people oon thi subject,
however, youu siund like yoou know whzt you’re taqlking
about! Thanks
Hi mates, goold arrticle andd nice urtging commented here,
I am in ffact enjnoying byy these.
Thank you for your sharing. I am worried that I lack creative ideas. It is your article that makes me full of hope. Thank you. But, I have a question, can you help me?