[
https://issues.apache.org/jira/browse/TAP5-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18055634#comment-18055634
]
Hudson commented on TAP5-2816:
------------------------------
FAILURE: Integrated in Jenkins build Tapestry ยป tapestry-java-17-freestyle #180
(See
[https://ci-builds.apache.org/job/Tapestry/job/tapestry-java-17-freestyle/180/])
TAP5-2816: SeleniumTestCase replace By.link with By.xpath locator (benw: rev
6ff6ded4047f55d7a5fd3b6027a500e04015a140)
* (edit)
tapestry-core/src/test/groovy/org/apache/tapestry5/integration/appfolder/AppFolderTests.groovy
* (edit)
tapestry-test/src/main/java/org/apache/tapestry5/test/SeleniumTestCase.java
* (edit) tapestry-upload/src/test/webapp/Ajaxified.tml
> Selenium By.link might fail due to security manager veto
> --------------------------------------------------------
>
> Key: TAP5-2816
> URL: https://issues.apache.org/jira/browse/TAP5-2816
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-test
> Affects Versions: 5.10.0
> Reporter: Ben Weidig
> Assignee: Ben Weidig
> Priority: Major
>
> The integration tests use a {{By.link}} locator to click on links.
> Selenium 4.12 uses a JavaScript "atom" to execute {{By.linkText}} by
> iterating over {{document.links}} and reading the 'text' property.
> Depending on the Firefox version and profile, the XPConnect Security Manager
> might veto this script.
> To fix this, we should use browser native selectors (XPath or CSS), as
> Selenium uses them directly, not via JS.
> This will require a few adaptions in tests (e.g. case-senstivitiy of the link
> text).
> This might break code of people using SeleniumTestCase for their own tests as
> a base, but it should be easy to adapt the tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
