Is there a similar way to ensure that all wicket:message key resources exist?

//Swanthe

Igor Vaynberg wrote:
if you want the removal of wicket:id to fail turn on component use
check in debug settings.

-igor

On Tue, Mar 10, 2009 at 3:12 AM, Swanthe Lindgren
<swanthe.lindg...@megasol.se> wrote:
Hi all
I have begun unit testing my wicket pages and one of the most basic tests I
want to do is to make sure each and every page can render properly. The
WicketTester.assertRenderedPage() looks like a good approach but it doesnt
seam to care about the HTML. If I remove a wicket:id from the markupfile,
the test is still passed.
Is this correct or might there be something else I have done wrong?

//Swanthe




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org





---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to