You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Frank Bille Jensen (JIRA)" <ji...@apache.org> on 2008/04/20 20:46:27 UTC
[jira] Updated: (WICKET-1214) WicketTester#startPanel does not work
(correctly)
[ https://issues.apache.org/jira/browse/WICKET-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Bille Jensen updated WICKET-1214:
---------------------------------------
Fix Version/s: (was: 1.4-M1)
1.4-M2
> WicketTester#startPanel does not work (correctly)
> -------------------------------------------------
>
> Key: WICKET-1214
> URL: https://issues.apache.org/jira/browse/WICKET-1214
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.4-M1
> Reporter: Martijn Dashorst
> Fix For: 1.4-M2
>
>
> WicketTester#startPanel(class<? extends Panel>) does not work with the assertions:
> WicketTester tester = new WicketTester();
> tester.startPanel(HelloWorldPanel.class);
> tester.assertLabel("message", "Hello, World!");
> Will throw an exception because "message" can't be found. In the response page the panel is added with component identifier "panel". However as a tester I expect to be able to assert the components directly without having to know what happens internally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.