wicket-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Grigorov <mgrigo...@apache.org>
Subject Re: [jira] Resolved: (WICKET-1214) WicketTester#startPanel does not work (correctly)
Date Sat, 27 Nov 2010 17:37:20 GMT
I think this one deserves an entry in the migration page.
It will break some tests in the users' applications.

On Sat, Nov 27, 2010 at 3:47 PM, Juergen Donnerstag (JIRA)
<jira@apache.org>wrote:

>
>     [
> https://issues.apache.org/jira/browse/WICKET-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Juergen Donnerstag resolved WICKET-1214.
> ----------------------------------------
>
>    Resolution: Fixed
>
> > 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: Juergen Donnerstag
> >             Fix For: 1.5-M4
> >
> >
> > 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.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message