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. For more options, visit https://groups.google.com/d/optout.
