Sure. But from the beginning, I was looking for a way not to write the famous 2 lines of code (see above) for each page and component.
I'll have a look for sure at your lib, the Selenium integration is promising. :-) On Wed, Nov 25, 2009 at 10:25 AM, Kent Tong <[email protected]> wrote: > > > > Pierre Goupil wrote: > > > > I use it, and what I'm looking for is a mean to ensure my test coverage. > > > > If you're using TDD, you will have developed the page and the unit test for > that > page at the same time and by definition you won't have a page that is not > tested. > > ----- > -- > Kent Tong > Better way to unit test Wicket pages ( > http://wicketpagetest.sourceforge.net) > -- > View this message in context: > http://old.nabble.com/Wicket-tester-test-coverage-tp26505428p26509669.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Rien de grand ne s'est accompli dans le monde sans passion. (G.W.F. Hegel, philosophe allemand)
