You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "werpu (via GitHub)" <gi...@apache.org> on 2023/03/10 15:01:27 UTC

[GitHub] [myfaces] werpu commented on pull request #548: Use Java11+ HTTP Client for Selenium

werpu commented on PR #548:
URL: https://github.com/apache/myfaces/pull/548#issuecomment-1463930047

   Hi sorry to jump in here so late.
   
   Hi following fixed it for me  options.addArguments("--remote-allow-origins=*");
   aka chrome options remote-allow-origins=*
   
   This basically reduces the security of chrome on the latest builds to allow websocket connections again, which seems to be the issue why the tests fail with the remote connection error on the chrome driver!
   Not sure where to add this in our myfaces tests, this is probably a selenium setting you can pass down to the webdriver!
   (On the jakarta codebase I instantiate the selenium webdriver programmatically hence I put it into the code itself)
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@myfaces.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org