We write tests first and use Wicket's built-in testing. It has some quirks so you may have to spend time with figuring out how to click an AjaxCheckBox, for instance.
The tests target the logic of the view, such as "when clicking here, that other thing should be disabled". Good test coverage really pays off when you have 20 different webapps and need to work some here and some there. /Per On Mon, Jan 25, 2010 at 3:52 AM, Kent Tong <k...@cpttm.org.mo> wrote: > > For functional testing, I'd suggest Selenium. > > For unit testing of Wicket pages, I'd suggest "Wicket Page Test" > (http://wicketpagetest.sourceforge.net). > > ----- > -- > Kent Tong > Better way to unit test Wicket pages ( > http://wicketpagetest.sourceforge.net) > Books on CXF, Axis2, Wicket, JSF (http://http://agileskills2.org) > -- > View this message in context: > http://old.nabble.com/functional-testing-tp27278781p27301553.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
