Switch from Selenium to Cuprite #5476
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Review app deployed to https://cpd-ecf-review-5476-web.test.teacherservices.cloud |
We have noticed that our CI is hanging randomly on the feature specs that are using the Javascript Selenium webdriver. It appears to be a HTTP timeout that Selenium experiences, though its not easy to replicate or debug. In an effort to fix the issue we can move to Cuprite, which is a pure Ruby driver for Capybara. An issue with doing this is that the latest versions of `axe-core-api` have not been updated for Cuprite support (they expect Selenium). It does, however, work with versions prior to `4.3` so we can pin the version. This should get rid of the flakiness as its removing Selenium, which is where it falls down. I'm still not clear on why Selenium is flakey though.
ethax-ross
force-pushed
the
3951-switch-to-cuprite
branch
from
ed622e0 to
477b525
Compare
|
Closing as cuprite seems flakey |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
We have noticed that our CI is hanging randomly on the feature specs that are using the Javascript Selenium webdriver. It appears to be a HTTP timeout that Selenium experiences, though its not easy to replicate or debug.
Changes proposed in this pull request
In an effort to fix the issue we can move to Cuprite, which is a pure Ruby driver for Capybara. An issue with doing this is that the latest versions of
axe-core-apihave not been updated for Cuprite support (they expect Selenium). It does, however, work with versions prior to4.3so we can pin the version.Guidance to review
This should get rid of the flakiness as its removing Selenium, which is where it falls down. I'm still not clear on why Selenium is flakey though.
There are some nuances with how Cuprite behaves so the tests have minor updates to reflect that.