We use @AuthorizedInstantiation. But what we're looking for is not a way to inject the credentials but rather a way to access directly a protected page in unit tests.
We know how to provide credentials and browse to the page but find it dangerous: what if the credentials change, what if the Website layout changes... ? Regards, Pierre On Mon, Jan 4, 2010 at 12:36 PM, Martin Makundi < martin.maku...@koodaripalvelut.com> wrote: > Hi! > > Depends on your login but ofcourse wicket is a whitebox so you can > inject any credentials you want. But visit the login page first to > create session. > > ** > Martin > > 2010/1/4 Pierre Goupil <goupilpie...@gmail.com>: > > Hello all, > > > > Is there a way to access directly a page in Wicket tester? I mean: > > by-passing the login page in order not to execute the whole workflow > leading > > to a certain page. > > > > We use, of course, @AuthorizedInstantiation-based login. We've found > > examples where people provide directly the credentials to the login form > and > > then browse to the desired page, but I was wondering whether something > more > > "direct" existed. > > > > Regards, > > > > Pierre > > > > > > -- > > Ad augusta per angusta > > > > Des résultats grandioses par des voies étroites > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Ad augusta per angusta Des résultats grandioses par des voies étroites
