Thanks for all your detailed responses. I'm seeing multiple solutions for the 'problem', so I'll try a bunch out. I guess I completely skipped over the *waitCondition* multiple times.
- *(...) Testing for invisibility of asynchronously loaded page elements is always problematic because without waiting the test would pass too quickly and falsely!* I think generally, a user would usually would be able to verify something rightfully isn't being displayed, not because it doesn't show after an arbitrary time interval, but because similar stuff *is* happening, and that specific thing isn't. Also, depending on the machine running the tests, how long to wait for is very tricky, so to be safe you specify a timeout period that is significantly longer than required. Being able to somehow specify those criteria above would improve test speed I think. Like: as an admin, when I press button A, I should see new buttons B&C. As a user, when I press button A, I should see new button B and not C. In that case, if B shows up and not C, you don't need to wait your full timeout time -- 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/2bd09d17-e8b2-450d-b3a4-3c8ebe36dce1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
