chromedriver 115 needs Chrome for Testing
After We updated chromedriver 115 on our MacBook with
chromedriver 115 needs Chrome for Testing

Google Chrome for Testing
After We updated chromedriver 115 on our MacBook with
brew upgrade chromedriver
We cannot run robot framework anymore. It said “No browser is open” or something. But we heard there is something new about Chrome for Testing that be designed by Automate Testing…BRA BRA BRA…
TLDR: chromedriver 115 needs Chrome for Testing
How to fix it
- Download Chrome for Testing ( ref1: https://github.com/GoogleChromeLabs/chrome-for-testing , ref2: https://developer.chrome.com/blog/chrome-for-testing/ )
npx @puppeteer/browsers install chrome@stable
It will download latest version of Chrome for Testing at ./chrome folder.
- Copy/Cut “Google Chrome for Testing.app” into /Application
- Fix some MacOS permission about Networking
xattr -csr 'Google Chrome for Testing.app'
Try upper command first. Run Robot again. If it’s not work (like ours) try more command with…
sudo codesign --force --deep --sign - 'Google Chrome for Testing.app'
We work here. (ref: https://apple.stackexchange.com/questions/394986/macos-firewall-do-you-want-the-application-google-chrome-app-to-accept-incom )
- Allow some MacOS permission about Files and Folders that you can click Allow button on Popup Window.
We hope you can run Robot Framework again.
메타데이터
- post_id
- ada09f5e4dc8
- slug
- chromedriver-115-needs-chrome-for-testing-ada09f5e4dc8
- url
- https://medium.com/@paween-p/chromedriver-115-needs-chrome-for-testing-ada09f5e4dc8
- canonical_url
- https://medium.com/@paween-p/chromedriver-115-needs-chrome-for-testing-ada09f5e4dc8
- author_url
- https://medium.com/@paween-p
- status
- ok
- fetched_at
- 2026-06-29 01:02:39