Ramesh, When you set atCheckWaiting to false in your config script then nothing happens because it is the default. It basically means - only ever try to execute an at checker once and if it fails then throw an AssertionError (if assertions are enabled, which again is the default). In other words, do not wrap at checking in a waitFor block which happens if atCheckWaiting is set to any value listed at https://gebish.org/manual/current/#content-dsl-wait.
Marcin On Sun, Sep 15, 2019 at 8:20 AM GebUser <[email protected]> wrote: > Hi Marcin, > Can you please explain what is actually happens if we set atCheckWaiting > to false. Will my tests run faster if I set Setting atCheckWaiting to false > globally? > I noticed setting atCheckWaiting to false makes tests run faster because > it took le wait and check everything in at block. Can you please correct me > if I am wrong? > > > Thanks > Ramesh > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/geb-user/50ef7a5c-b999-4bbc-804f-e69f3260c79f%40googlegroups.com > . > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/geb-user/CA%2B52dQSYkEXt3JcFkYGF-XYjnsX0oSpxEMAMtK22sQWGwO%2BzWw%40mail.gmail.com.
