-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
⚙️ [i32] - resolve selenium error #750
Conversation
desired_capabilities is deprecated. This commit changes the way we initialize selenium driver per the newer requirements when dual booting. At this point, it resolves the error how there are still local timeout issues. ref: - https://github.com/SeleniumHQ/selenium/blob/trunk/rb/lib/selenium/webdriver/remote/driver.rb#L32 Issue: - scientist-softserv#64
This change allowed feature specs to run locally. I am not sure why this fixed things or why we are even able to connect to hyku.test so this may be a smell and something to dive into later. For now it unblocks devs though!
@@ -235,4 +235,4 @@ services: | |||
environment: | |||
- JAVA_OPTS=-Dwebdriver.chrome.whitelistedIps= | |||
- VIRTUAL_PORT=7900 | |||
- VIRTUAL_HOST=chrome.ams.test | |||
- VIRTUAL_HOST=chrome.hyku.test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NOTE: I don't understand why this change fixes it. And I also don't understand why we can connect to hyku.test when it's not defined in our docker setup. 🤔
No other docker projects are running so this must be coming from gbh's setup somehow. I think it's ok to proceed for now since it unblocks us however Rob/devops should prob look into it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work! That is so weird about hyku.test 🤔
desired_capabilities is deprecated. This PR changes the way we initialize selenium driver per the newer requirements when dual booting.
It also changes the docker-compose.yml file to allow devs to run feature specs locally.
ref:
Issue:
I confirmed that feature specs can run locally in rails 5 and 6. There are still failures in rails 6 but we'll handle that in a separate ticket.
rails_5_1?
rails 6