[Wicket-user] Problem in unit tests

[Iman RahmatiZadeh]

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 cant work with it. I can't implement another MockWebApplication, because getSession() in WebApplication has package access, and it's critical for setting up the session. Has anybody solved such problems ? Does anybody know the preferred way of unit testing (not functional testing) the pages ?

Regards
Iman