[
https://issues.apache.org/jira/browse/TAP5-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18057182#comment-18057182
]
Hudson commented on TAP5-2817:
------------------------------
FAILURE: Integrated in Jenkins build Tapestry ยป
tapestry-javax-java-17-freestyle #111 (See
[https://ci-builds.apache.org/job/Tapestry/job/tapestry-javax-java-17-freestyle/111/])
TAP5-2817: SeleniumTestCase rename container constants (benw: rev
5ad6db43bcecb0a18b5a790d2332fb9978bd9b74)
* (edit)
tapestry-test/src/main/java/org/apache/tapestry5/test/TapestryTestConfiguration.java
* (edit)
tapestry-test/src/main/java/org/apache/tapestry5/test/SeleniumTestCase.java
> Upgrade Selenium
> ----------------
>
> Key: TAP5-2817
> URL: https://issues.apache.org/jira/browse/TAP5-2817
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-test
> Reporter: Ben Weidig
> Assignee: Ben Weidig
> Priority: Critical
>
> The {{tapestry-test}} project currently uses Selenium 4.12.1 (2023-09) and
> Selenium Legacy Remote Control 4.5.0.
> {{SeleniumTestCase}} is not designed to work with the current WebDriver
> abstraction but Selenium instead.
> This leads to certains tasks that the newer WebDriver supports natively and
> out-of-the-box to be reimplmeneted, and sometimes even in incompatible ways
> with modern Browsers.
> That's why thge Legacy Remote Control dependency should be removed, and
> Selenium be updated to the latest version.
> {{SeleniumTestCase}} needs to be adapted.
> This will introduce breaking changes if anyone used {{SeleniumTestCase}} as
> their base class, as many of the delegation/helper methods are redundant and
> can be used more easily via the driver.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
