Hi, What you can do is scan all Page classes (or Panel classes, etc) on the class-path and check if there are tests for them.
Put this code in a unit test. Fail the test if you find a class without accompanying test. You can use this example to get started with the class path scanning: http://stuq.nl/weblog/2009-11-01/automatically-test-your-wicket-panel-html-markup Regards, Daan van Etten On Wed, 2009-11-25 at 09:23 +0100, Pierre Goupil wrote: > I use it, and what I'm looking for is a mean to ensure my test coverage. > > > On Wed, Nov 25, 2009 at 6:13 AM, Kent Tong <[email protected]> wrote: > > > > > > > > > Pierre Goupil wrote: > > > > > > So I'm looking for a way to list all Page instances in a Wicket app, > > which > > > could then allow me to be sure that they are all covered by a test. And > > > when > > > it's done maybe I could use the same system in order to ensure that > > > Selenium > > > (the automated functional testing tool) has covered all my pages as well > > > (more deeply). > > > > > > > What you need is TDD. Once you adopt TDD, you will have every page 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-tp26505428p26507647.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] > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
