-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
Update Selenium #169
Labels
Milestone
Comments
I thought we were already using a newer version, will look into that. |
Yeah, it was done in #159 (at least to 3.11.0), we still need to release a new version though. |
thc202
added a commit
to thc202/zest
that referenced
this issue
Jun 22, 2018
Update Selenium to latest version. Fix zaproxy#169 - Update Selenium Related to zaproxy/zaproxy#4776 - Update Selenium
thc202
added a commit
to thc202/zest
that referenced
this issue
Jun 25, 2018
Update Selenium to latest version. Fix zaproxy#169 - Update Selenium Related to zaproxy/zaproxy#4776 - Update Selenium
thc202
added a commit
to thc202/zest
that referenced
this issue
Jun 25, 2018
Update Selenium to latest version. Fix zaproxy#169 - Update Selenium Related to zaproxy/zaproxy#4776 - Update Selenium
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While the Zest Runner works fine with the current version of Selenium included in it, we (at a major German company) have some headaches with it. Our source scan by Nexus IQ yields "Policy D1 High Security Threat V1" with highest level for the following two dependencies:
org.eclipse.jetty:jetty-util:9.4.1.v2017012
xerces:xercesImpl:2.11.0
org.eclipse.jetty:jetty-util:9.4.1.v20170120 comes via org.seleniumhq.selenium:selenium-server:jar:3.4.0
xerces:xercesImpl:2.11.0 comes via org.seleniumhq.selenium:selenium-server:jar:3.4.0 and/or org.seleniumhq.selenium:selenium-java:jar:3.4.0
I tried to update Selenium to the next version, 3.5.1, but was not successful because this change caused one unit test to fail. Can you please do the update?
The text was updated successfully, but these errors were encountered: