You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Juergen Donnerstag (JIRA)" <ji...@apache.org> on 2011/04/03 17:54:05 UTC

[jira] [Resolved] (WICKET-3085) Support for starting FormComponentPanel in WicketTester

     [ https://issues.apache.org/jira/browse/WICKET-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juergen Donnerstag resolved WICKET-3085.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5-RC4

> Support for starting FormComponentPanel in WicketTester
> -------------------------------------------------------
>
>                 Key: WICKET-3085
>                 URL: https://issues.apache.org/jira/browse/WICKET-3085
>             Project: Wicket
>          Issue Type: New Feature
>          Components: wicket-core
>    Affects Versions: 1.4.12
>         Environment: All
>            Reporter: Per Newgro
>            Assignee: Juergen Donnerstag
>             Fix For: 1.5-RC4
>
>
> Normally we use a validator and an error feeback behavior for components like textfields and ddcs. These simple components are placed on a panel and can simply be tested by WicketTester.
> Now we use a FormComponentPanel to provide a way for adding a validator and this error feedback behavior to a container. But it can't be tested simply with the WicketTester because it can't be started.
> We could create a helper panel and test it there. But it would be great if wicket could support testing  this component as easy as panels and pages.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira