You probably could extract the navigation instead of content. It's just hard to provide the best guidance given that I only have part of the picture on my end. That's why I'm only giving you pointers and hopefully they will get you on the right track.
On Wed, Jan 24, 2018 at 8:31 AM, Samuel Rossinovic < [email protected]> wrote: > Hmm. Doing that won't avoid duplicating Pages (If I could externalize the > navigation bits, I would only need the one Page class). Also, I think I > cannot reuse the at() verification closure, only content. > Still - it's a good place to start from. I will have a look at > implementing. Thanks! > > On Wednesday, January 24, 2018 at 6:23:59 AM UTC+11, Marcin Erdmann wrote: >> >> How about extracting the non-navigation related content to modules (one >> content module per page) and reusing that? >> >> On Mon, Jan 22, 2018 at 5:59 AM, Samuel Rossinovic <[email protected] >> > wrote: >> >>> 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/ms >>> gid/geb-user/436fb583-3edd-487e-a247-6c50414ac048%40googlegroups.com >>> <https://groups.google.com/d/msgid/geb-user/436fb583-3edd-487e-a247-6c50414ac048%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/fccc57fe-1d00-4607-bb3b-5f61447484fc%40googlegroups.com > <https://groups.google.com/d/msgid/geb-user/fccc57fe-1d00-4607-bb3b-5f61447484fc%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%2B52dQShwW8ye07x0e49Dcpko_Bvt_6ik0CJ0uMVBBCs4ZsaeA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
