Hi. The app I am testing is a single page app. The various pages do not have their own urls. Rather, pages are browsed through a series of clicks on navigation buttons (selecting a main menu item, then selecting a sub-menu, etc). Building on a prev discussion <https://groups.google.com/d/msg/geb-user/YArbpe-aWzc/mrSQSAasCgAJ>, I have built the buttons as content in the page. This resulted in a set of Pages, all inheriting the common navigation content, as part of their parent Page. I am now trying to extend testing across to another app: very similar pages, but different navigation, so different menu/sub menu items.
The problem I'm facing now, is while I'd like to reuse the pages (at() verifiers & content), the navigation is baked-into the pages as content. I think I'd be in a better situation had the pages been navigable through their url. Then, navigation is extracted-out to Browser.to() et al, and doesn't pollute the Page. Possibly someone who stumbled on a similar situation can suggest a solution: maybe somehow piggyback the navigation code onto Browser? Thanks! -- 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/436fb583-3edd-487e-a247-6c50414ac048%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
