Skip to content
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

Merged
merged 2 commits into from
Aug 11, 2023

Conversation

ShanaLMoore
Copy link
Collaborator

@ShanaLMoore ShanaLMoore commented Aug 11, 2023

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?

Finished in 4 minutes 12.4 seconds (files took 16.21 seconds to load)
54 examples, 0 failures, 18 pending

rails 6

Finished in 2 minutes 47.8 seconds (files took 16.44 seconds to load)
54 examples, 21 failures, 18 pending

Screen Recording 2023-08-11 at 10 02 33 AM

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
@ShanaLMoore ShanaLMoore changed the title ⚙️ this commit addresses a deprecated pattern for Selenium ⚙️ Selenium error Aug 11, 2023
@ShanaLMoore ShanaLMoore changed the title ⚙️ Selenium error ⚙️ [i32] - Selenium error Aug 11, 2023
@ShanaLMoore ShanaLMoore marked this pull request as ready for review August 11, 2023 16:17
@ShanaLMoore ShanaLMoore marked this pull request as draft August 11, 2023 16:56
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!
@ShanaLMoore ShanaLMoore marked this pull request as ready for review August 11, 2023 17:09
@ShanaLMoore ShanaLMoore marked this pull request as draft August 11, 2023 17:10
@ShanaLMoore ShanaLMoore marked this pull request as ready for review August 11, 2023 17:12
@ShanaLMoore ShanaLMoore changed the title ⚙️ [i32] - Selenium error ⚙️ [i32] - resolve selenium error Aug 11, 2023
@@ -235,4 +235,4 @@ services:
environment:
- JAVA_OPTS=-Dwebdriver.chrome.whitelistedIps=
- VIRTUAL_PORT=7900
- VIRTUAL_HOST=chrome.ams.test
- VIRTUAL_HOST=chrome.hyku.test
Copy link
Collaborator Author

@ShanaLMoore ShanaLMoore Aug 11, 2023

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.

Copy link
Collaborator

@kirkkwang kirkkwang left a 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 🤔

@ShanaLMoore ShanaLMoore merged commit d58bde0 into develop Aug 11, 2023
6 checks passed
@orangewolf orangewolf deleted the i64-resolve-selenium-error branch September 11, 2023 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants