OK! On which object? Is there a way to do: setAuthenticated(true)? <:^-)
On Mon, Jan 4, 2010 at 12:44 PM, Martijn Dashorst <
martijn.dasho...@gmail.com> wrote:
> You probably store the credentials (or isAuthenticated() == true) in
> the session. Just set the credentials *on* your session during
You probably store the credentials (or isAuthenticated() == true) in
the session. Just set the credentials *on* your session during
testing.
Martijn
On Mon, Jan 4, 2010 at 12:32 PM, Pierre Goupil wrote:
> Hello all,
>
> Is there a way to access directly a page in Wicket tester? I mean:
> by-pass
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 Websit
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 :
> Hello all,
>
> Is there a way to access directly a page in Wicket tester? I mean:
> by-passing the login
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
