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:
see IResourceSettings#setThrowExceptionOnMissingResource(boolean)
-igor
On Wed, Mar 11, 2009 at 8:57 AM, Swanthe Lindgren
swanthe.lindg...@megasol.se wrote:
Is there a similar way to ensure that all wicket:message key resources
exist?
//Swanthe
Igor Vaynberg wrote:
if you want the
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
Message-
From: Swanthe Lindgren swanthe.lindg...@megasol.se
Sent: Tuesday, March 10, 2009 5:12 AM
To: users@wicket.apache.org
Subject: test page rendering
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
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
