jonnybot0 commented on PR #271:
URL: https://github.com/apache/groovy-geb/pull/271#issuecomment-2895191220

   Hm. Okay, I can sorta reproduce the issue by reducing the timeout in the JS 
(see this patch). Only running it for the content that failed in #188, but it 
works equally well for the `link`. Fails on about 11/100 runs.
   
   ```
   diff --git a/module/geb-core/src/test/groovy/geb/PageOrientedSpec.groovy 
b/module/geb-core/src/test/groovy/geb/PageOrientedSpec.groovy
   index d1d164a8..b738b12e 100644
   --- a/module/geb-core/src/test/groovy/geb/PageOrientedSpec.groovy
   +++ b/module/geb-core/src/test/groovy/geb/PageOrientedSpec.groovy
   @@ -36,7 +36,7 @@ class PageOrientedSpec extends GebSpecWithCallbackServer {
                        <script type="text/javascript" charset="utf-8">
                        setTimeout(function() {
                            document.body.innerHTML += '<div 
id="dynamic">dynamic</div>';
   -                    }, 100);
   +                    }, 1);
                        </script>
                    </head>
                    <body>
   @@ -49,7 +49,6 @@ class PageOrientedSpec extends GebSpecWithCallbackServer {
        }
    
        def setup() {
   -        driver.webClient.options.javaScriptEnabled = false
        }
    
        def "verify our server is configured correctly"() {
   @@ -90,7 +89,7 @@ class PageOrientedSpec extends GebSpecWithCallbackServer {
            at PageOrientedSpecPageA
    
            where:
   -        contentName << ["link", "linkUsingPageInstance"]
   +        [contentName, index] << [["linkUsingPageInstance"], 
(1..100).toList()].combinations()
        }
    
        @Unroll
   ```
   
   Having the JS that's at the root of the problem and the tests that require 
it in a separate spec still seems the better path. 


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to