Poundex opened a new issue, #188:
URL: https://github.com/apache/groovy-geb/issues/188

   - **ParallelExecutionSpec** - _Flaky in CI_
   ```
   ParallelExecutionSpec > GebReportingSpec supports parallel execution at 
feature level FAILED
       Condition not satisfied:
   
       reportFileTestCounterPrefixes("SpecRunningIterationsInParallel1") == 
(["000"] * 2) + (1..4)*.toString()*.padLeft(3, "0")
       |                                                                 |      
     |    |         |           |
       [000, 000, 001, 002, 003, 004, 004]                               false  
     |    |         |           [001, 002, 003, 004]
                                                                                
     |    |         [1, 2, 3, 4]
                                                                                
     |    [000, 000, 001, 002, 003, 004]
                                                                                
     [000, 000]
           at geb.spock.ParallelExecutionSpec.GebReportingSpec supports 
parallel execution at feature level(ParallelExecutionSpec.groovy:186)
   
   ```
   
   - **PageOrientedSpec** - _Flaky in CI_
   ```
   PageOrientedSpec > verify the Page API works for '#contentName' content > 
verify the Page API works for 'linkUsingPageInstance' content FAILED
       org.openqa.selenium.StaleElementReferenceException: The element seems to 
be disconnected from the DOM.  This means that a user cannot interact with it.
       For documentation on this error, please visit: 
https://selenium.dev/exceptions/#stale_element_reference
       Build info: version: '4.2.2', revision: '683ccb65d6'
       System info: host: '075353d81e19', ip: '192.168.176.3', os.name: 
'Linux', os.arch: 'amd64', os.version: '5.15.0-1057-aws', java.version: 
'11.0.24'
       Driver info: driver.version: IDataDriver
           at 
app//org.openqa.selenium.htmlunit.HtmlUnitDriver.assertElementNotStale(HtmlUnitDriver.java:899)
           at 
app//org.openqa.selenium.htmlunit.HtmlUnitWebElement.assertElementNotStale(HtmlUnitWebElement.java:591)
           at 
app//org.openqa.selenium.htmlunit.HtmlUnitWebElement.verifyCanInteractWithElement(HtmlUnitWebElement.java:249)
           at 
app//org.openqa.selenium.htmlunit.HtmlUnitWebElement.click(HtmlUnitWebElement.java:131)
           at 
app//geb.navigator.DefaultNavigator.click(DefaultNavigator.groovy:672)
           at 
app//geb.navigator.DefaultNavigator.click(DefaultNavigator.groovy:687)
           at 
app//geb.content.TemplateDerivedPageContent.click(TemplateDerivedPageContent.groovy:83)
           at geb.PageOrientedSpec.verify the Page API works for '#contentName' 
content(PageOrientedSpec.groovy:73)
   ```
   
   - **DateInputSpec** - _Functionality broken in recent ChromeDriver_
   It seems this test is failing due to broken functionality in recent versions 
of ChromeDriver, where setting a value of an `<input type="datetime-local" />` 
does not work as expected. There is some discussion of the issue on [this 
php-webdriver 
thread](https://github.com/php-webdriver/php-webdriver/issues/709). There is an 
[existing ChromeDriver ticket](https://issues.chromium.org/issues/42322342) but 
it doesn't look like it's getting fixed. A common workaround seems to be using 
JavaScript to set the value, rather than manipulating directly, [like in this 
example](https://github.com/teamcapybara/capybara/blob/e8874a1cbc3e967b74621fb243c0ae514625900f/lib/capybara/selenium/node.rb#L255).


-- 
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