I admit being tempted to just roll back to Geb 2.2 and abandon the topic. But that cannot be the solution, right?
So I built up a new Geb/Cucumber Maven project, boiling it down to an MCVE (see attached zip file). At least now I am able to link the problem to JavaFX: We developed a little GroovyFX dialogue running in a separate thread, allowing to interact with the running Maven Cucumber job (pausing at will, evaluating some expressions etc.). And now the MissingPropertyException arises if - Geb has version 2.3.1 AND - JavaFX "Application" is launched during Cucumber World hook. Reverting to Geb 2.2 OR removing the GroovyFX call both remove the Exception. Now I am completely lost! How can those two seemingly unrelated "things" interfere??? :-( Any ideas, anyone? Klaus PS: Stacktrace from MCVE project for reference: groovy.lang.MissingPropertyException: Unable to resolve atChecker as content for automation.EcosiaStartPage, or as a property on its Navigator context. Is atChecker a class you forgot to import? at geb.content.PageContentSupport.propertyMissing(PageContentSupport.groovy:47) at geb.content.PageContentSupport$propertyMissing.call(Unknown Source) at geb.Page.propertyMissing(Page.groovy:112) at geb.Page.getShouldVerifyAtImplicitly(Page.groovy:477) at geb.Browser.to(Browser.groovy:560) at geb.Browser$to$1.callCurrent(Unknown Source) at geb.Browser.to(Browser.groovy:537) at geb.Browser$to$0.callCurrent(Unknown Source) at geb.Browser.to(Browser.groovy:526) at geb.Browser.to(Browser.groovy) at geb.binding.BindingUpdater$InvocationForwarding.doCall(BindingUpdater.groovy:106) at automation.EcosiaSteps$_run_closure1.doCall(EcosiaSteps.groovy:6) at ✽.I open Ecosia(src/test/resources/features/Ecosia.feature:4) Am Donnerstag, 16. Mai 2019 10:28:26 UTC+2 schrieb Klaus L.: > > Thanks for responding :) > > Providing an MCVE is not that easy here though, because we have "modular" > setup with a shared library (bringing in a large GebConfig and necessary > dependencies), and actual product-related test projects. So I would have to > flatten the whole structure and compose a whole new small test project e.g. > for google.com :( > > @Trinidad: Thanks for the reference! > However it seems you are on a quite outdated version of cucumber (1.2.5 > vs. 4.3.x), so I do not know if we are comparable here. > > But focusing on the other difference (Gradle vs. Maven), I played around > with the configs and found something peculiar: > When I modify my maven-failsafe-plugin config to reuse the Maven JVM > process ( <forkCount>0</forkCount> ) then the error disappears! > This is no feasible workaround for me for other reasons, but an > interesting observation, I think :-) > > > > Am Mittwoch, 15. Mai 2019 05:13:29 UTC+2 schrieb Trinidad Esparza: >> >> We recently updated the Geb project examples with all proper dependencies >> . >> >> https://github.com/geb/geb-example-cucumber-jvm/blob/master/build.gradle >> >> If this doesn’t work let us know but please provide example code. > > -- You received this message because you are subscribed to the Google Groups "Geb User Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/geb-user/86515f31-c5e7-4e03-aabb-69f898adc1bc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
<<attachment: geb-atchecker-mcve.zip>>
