-
Notifications
You must be signed in to change notification settings - Fork 30
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
Repair drone webdriver for firefox and chrome, cleanup #158
base: master
Are you sure you want to change the base?
Conversation
Don't merge this pull request, but keep it on hold. Only open problem: download of chromdriver fails. When the next drone release is done, I will come back to this pull request. At least the cleanup will still be relevant. |
…an#153) Bumps [org.apache.httpcomponents.core5:httpcore5](https://github.com/apache/httpcomponents-core) from 5.2.2 to 5.2.3. - [Changelog](https://github.com/apache/httpcomponents-core/blob/master/RELEASE_NOTES.txt) - [Commits](apache/httpcomponents-core@rel/v5.2.2...rel/v5.2.3) --- updated-dependencies: - dependency-name: org.apache.httpcomponents.core5:httpcore5 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…quillian#155) Bumps com.mycila:license-maven-plugin from 4.2 to 4.3. --- updated-dependencies: - dependency-name: com.mycila:license-maven-plugin dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…llian#159) Bumps [xyz.rogfam:littleproxy](https://github.com/LittleProxy/LittleProxy) from 2.0.20 to 2.0.22. - [Release notes](https://github.com/LittleProxy/LittleProxy/releases) - [Changelog](https://github.com/LittleProxy/LittleProxy/blob/main/RELEASE_NOTES.md) - [Commits](LittleProxy/LittleProxy@v2.0.20...v2.0.22) --- updated-dependencies: - dependency-name: xyz.rogfam:littleproxy dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [org.apache.logging.log4j:log4j-bom](https://github.com/apache/logging-log4j2) from 2.20.0 to 2.21.0. - [Release notes](https://github.com/apache/logging-log4j2/releases) - [Commits](apache/logging-log4j2@rel/2.20.0...rel/2.21.0) --- updated-dependencies: - dependency-name: org.apache.logging.log4j:log4j-bom dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps `version.jacoco` from 0.8.10 to 0.8.11. Updates `org.jacoco:org.jacoco.core` from 0.8.10 to 0.8.11 - [Release notes](https://github.com/jacoco/jacoco/releases) - [Commits](jacoco/jacoco@v0.8.10...v0.8.11) Updates `org.jacoco:jacoco-maven-plugin` from 0.8.10 to 0.8.11 - [Release notes](https://github.com/jacoco/jacoco/releases) - [Commits](jacoco/jacoco@v0.8.10...v0.8.11) --- updated-dependencies: - dependency-name: org.jacoco:org.jacoco.core dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: org.jacoco:jacoco-maven-plugin dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…xed one real error (arquillian#163)
Bumps [org.apache.logging.log4j:log4j-bom](https://github.com/apache/logging-log4j2) from 2.21.0 to 2.22.0. - [Release notes](https://github.com/apache/logging-log4j2/releases) - [Commits](apache/logging-log4j2@rel/2.21.0...rel/2.22.0) --- updated-dependencies: - dependency-name: org.apache.logging.log4j:log4j-bom dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Drone 3.0.0-alpha.8 is out and should fix the problems. But it is build with Java 11. So we cannot wait for it if we want to do a final Java 1.8 release before switching to Java 11/JakartaEE10. Sorry for the commit chaos - I tried to sync my fork with recent changes, and probably broke something. If this breaks merging of the pull request, I can do a new one. |
The profiles "browser-firefox" and "browser-chrome" don't work since the update to Drone 3.0.0.Alpha7 (#91).
To run them, you have to combine the profile with a server profile:
mvn clean install -Pwildfly-remote,browser-firefox
The error for firefox is:
And the error for chrome:
Workaround/resolution: add a "browserVersion" property. Here, a wildcard works.
I asked in the drone github: arquillian/arquillian-extension-drone#418 whether this is a regression or an intentional change
I also removed the property
phantomjs.binary.path
, as there is a drone pull request to remove support for it: arquillian/arquillian-extension-drone#403And I commented
chromeDriverBinary
. The test will fail if the chromedriver is not placed in this directory, and it causes a warning when executing the tests:WARNUNG: Support for Legacy Capabilities is deprecated; You are sending the following invalid capabilities: [chromeDriverBinary, javascriptEnabled, phantomjs.binary.path]; Please update to W3C Syntax: https://www.selenium.dev/blog/2022/legacy-protocol-support/
But
chromeDriverBinary
might still be necessary, as the chrome profile will not work with recent version 117. The downloaded chromedriver does not support 117:It seems this is caused by the fact that the download for chromedriver has changed since 115: https://chromedriver.chromium.org/downloads/version-selection
This probably requires an update to latest Selenium, which has be done through Drone. There is also a Drone pull request for this: arquillian/arquillian-extension-drone#401
When downloading a matching chromedriver and setting the property "chromeDriver"...
<property name="chromeDriverBinary">c:\path\to\chromedriver.exe</property>
...it still fails:
And this is the point where I give up for now ;-).
Those pages https://stackoverflow.com/questions/75730109/how-to-overcome-invalid-status-code-403-text-forbidden-this-error-in-selenium and SeleniumHQ/selenium#11750 suggest to use a chrome argument
--remote-allow-origins=*
, but I could not make it work with Drone. This did not work:<property name="chromeArguments">--remote-allow-origins=*</property>
If Drone supports latest Selenium, it would be worth another look.