On Fri, 16 Nov 2007, Nino Saturnino Martinez Vazquez Wael wrote:
> A possible con are that the testing part of wicket could be improved by
> having more convenince methods. Also there seems to be some trouble
> testing if you use spring injection for your beans.
jdave-wicket has more convenience methods if that's an
option for you.
But what trouble have you run into with Spring beans? We
instantiate a MockApplicationContext and feed it to the
SpringComponentInstantiationListener of the Application
that WicketTester uses, and @SpringBeans just work.
> It's "pretty" hard doing stuff with the tester if you go beyond just
> selecting things, if you want to verify what the model contains. I could
Again this sounds strange to me.
You can just get the component you want and ask it, e.g.
wicketTester.getComponentFromLastRenderedPage("name").getModelObject().equals("Frank")
Best wishes,
Timo
--
Timo Rantalaiho
Reaktor Innovations Oy <URL: http://www.ri.fi/ >
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
