You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Swanthe Lindgren <sw...@megasol.se> on 2009/03/10 11:12:22 UTC
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
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-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: test page rendering
Posted by Igor Vaynberg <ig...@gmail.com>.
see IResourceSettings#setThrowExceptionOnMissingResource(boolean)
-igor
On Wed, Mar 11, 2009 at 8:57 AM, Swanthe Lindgren <
swanthe.lindgren@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 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
>> <sw...@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-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: test page rendering
Posted by Swanthe Lindgren <sw...@megasol.se>.
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
> <sw...@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-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: test page rendering
Posted by Igor Vaynberg <ig...@gmail.com>.
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
<sw...@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-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org