If the root element is something that contains multiple of these dynamic modules then you might need to use parametrised modules (there is a small entry about what a parameterised module is as part of the manual section on modules at http://gebish.org/manual/current/#modules). You could maybe use element index as a parameter of your module. Not sure if that helps but it should give you ideas.
Thanks for pointing out that moduleList() might me an issue with regards to auto-refreshing. It did not come to my mind initially that it will be something that will need special handling. The problem with "waitFor all javascript to be finished" is how do you define when it's finished? So far I've not found a generic answer to that as I believe that it's different from framework to framework (angular vs react) and sometimes even from action performed to action performed... I'm very glad that you're finding Geb helpful in writing your browser tests. On Thu, Dec 20, 2018 at 1:55 PM Martin de laat <[email protected]> wrote: > I will give your suggestion a go, thank you. the root element is actually > something that contains multiple of these dynamic modules so that might > cause some problems. (i created a geb Module for that as well, and it > stores these dynamic modules in a moduleList. ) > > Your idea for auto-refresh modules I think would be great because just > using the $() selector in the test is doing that as well. > Although I'm wondering how this would work with multiple modules in a > moduleList. If you are interacting with the first dynamic module, and it > disappears briefly, you wish to wait for it to re-appear instead of it now > selecting the second dynamic module (the 'new' first one in the list) > So maybe a waitFor all javascript stuff to be finished might help here > before refreshing, I don't know. > > For what it's worth, so far Geb is really helping with keeping the tests > clean, DRY (no redundancy) and implementation-independent so far whilst > still keeping things programmer-friendly > > I agree with your comment regarding the bad encapsulation > > -- > 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/1b23f42f-0cf1-4e8d-aa41-0d59a77329f9%40googlegroups.com > <https://groups.google.com/d/msgid/geb-user/1b23f42f-0cf1-4e8d-aa41-0d59a77329f9%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CA%2B52dQSXO%2BO4PidsDYE_Qm91Vf5JJs%2BjeO4mxLgv2Et-XGzz6A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
