You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Per Newgro (JIRA)" <ji...@apache.org> on 2010/09/29 10:43:33 UTC
[jira] Created: (WICKET-3085) Support for starting
FormComponentPanel in WicketTester
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
Affects Versions: 1.4.12
Environment: All
Reporter: Per Newgro
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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-3085) Support for starting
FormComponentPanel in WicketTester
Posted by "Juergen Donnerstag (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921864#action_12921864 ]
Juergen Donnerstag commented on WICKET-3085:
--------------------------------------------
Please provide a quickstart on how you do it today and how you envision the enhancements to work.
> 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
> Affects Versions: 1.4.12
> Environment: All
> Reporter: Per Newgro
>
> 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.
-
You can reply to this email to add a comment to the issue online.