Please see if WicketTester is more appropriate for you. An other
choice could be jWebUnit. But it requires a servlet container and is
pure html validation
Juergen
On 10/30/05, Iman RahmatiZadeh <[EMAIL PROTECTED]> wrote:
> Ok, Thanks. My mistake. In fact I was looking for something like the one y
Ok, Thanks. My mistake. In fact I was looking for something like the
one you suggested, delegating the whole scenario to my application
object. One more question, what's your strategy for unit testing ? From
what I saw in SortableTableHeadersTest ,would it be:
1- Setup the application, page and s
On 10/30/05, Iman RahmatiZadeh <[EMAIL PROTECTED]> wrote:
> Argh ! Unit testing is way too hard in wicket. I'm using a custom
> implementation of WebSession in my application. The problem arises when I
> use the MockWebApplication class for testing, which creates and uses
> WebSession for tests and
Argh ! Unit testing is way too hard in wicket. I'm using a custom
implementation of WebSession in my application. The problem arises when
I use the MockWebApplication class for testing, which creates and uses
WebSession for tests and my page classes which depend on my
implementation of WebSession c
