You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2011/02/22 14:53:38 UTC

[jira] Reopened: (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 ]

Martin Grigorov reopened WICKET-1214:
-------------------------------------

      Assignee: Martin Grigorov  (was: Juergen Donnerstag)

> 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
>            Assignee: Martin Grigorov
>             Fix For: 1.5-RC1
>
>         Attachments: patch1.patch
>
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira