[ 
https://issues.apache.org/jira/browse/MYFACES-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17689603#comment-17689603
 ] 

Werner Punz edited comment on MYFACES-4564 at 2/16/23 8:20 AM:
---------------------------------------------------------------

I think I found the issue, a timing issue as I expected... we have trigger -> 
findElement ... eval condition without timeouts or waits!

A quick fix is to increase the implicit wait time window for findElement, it 
probably is very low!

 

 


was (Author: werpu):
I think I found the issue, a timing issue as I expected... we have trigger -> 
findElement ... eval condition without timeouts or waits!

I will fix that with a conditional wait on the dom until the criteria is 
reached!

The entire test suite needs a rewrite in this direction but it seems that this 
exact test causes a bigger series of dom changes and runs into the default 
timeout window!

> Test failure in the table test on RC5 build
> -------------------------------------------
>
>                 Key: MYFACES-4564
>                 URL: https://issues.apache.org/jira/browse/MYFACES-4564
>             Project: MyFaces Core
>          Issue Type: Task
>    Affects Versions: 4.0.0-RC5
>            Reporter: Werner Punz
>            Assignee: Werner Punz
>            Priority: Major
>
> Report by [~volosied] 
> [INFO] [ERROR] Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time 
> elapsed: 21.554 s <<< FAILURE! - in 
> org.apache.myfaces.core.integrationtests.ajax.IntegrationTest
> [INFO] [ERROR] 
> org.apache.myfaces.core.integrationtests.ajax.IntegrationTest.testBasicTable  
> Time elapsed: 6.733 s  <<< ERROR!
> [INFO] org.openqa.selenium.TimeoutException: Expected condition failed: 
> waiting for 
> org.apache.myfaces.core.integrationtests.ajax.IntegrationTest$$Lambda$675/0x000000080085b040@2f54f746
>  (tried for 0 second(s) with 500 milliseconds interval)
> [INFO]  at 
> org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:87)
> ...
> This is very likey a timeout issue, given the new ajax code is somewhat 
> slower than the older one. The test needs to be fixed to wait for a dom 
> condition with a higher timeout window. I will take over this!
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to