You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Timo Rantalaiho (JIRA)" <ji...@apache.org> on 2008/10/29 11:21:44 UTC
[jira] Updated: (WICKET-1893) Extend FormTester to easily handle
CheckBox components.
[ https://issues.apache.org/jira/browse/WICKET-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timo Rantalaiho updated WICKET-1893:
------------------------------------
Affects Version/s: (was: 1.4-M4)
(was: 1.3.6)
(was: 1.5-M1)
1.4-M3
Assignee: Timo Rantalaiho
Have you tried
setValue(checkBoxId, "true");
?
Maybe it would be enough to just have overridden
setValue(checkBoxId, true)
I don't think that the getter is warranted -- what would be the use of it exactly?
> Extend FormTester to easily handle CheckBox components.
> -------------------------------------------------------
>
> Key: WICKET-1893
> URL: https://issues.apache.org/jira/browse/WICKET-1893
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.3.5, 1.4-M3
> Reporter: Minto van der Sluis
> Assignee: Timo Rantalaiho
> Priority: Minor
>
> Add methods to the FormTester to support unittesting CheckBox.
> The following methods could be added:
> public boolean getCheckBoxComponentValue(java.lang.String id);
> public void setValue(java.lang.String formComponentId, boolean value);
> When the given component ID is not a CheckBox (or one of its subclasses) then these methods could/should throw an exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.