You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Juergen Donnerstag (JIRA)" <ji...@apache.org> on 2010/11/27 15:47:13 UTC
[jira] Resolved: (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 ]
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.
Re: [jira] Resolved: (WICKET-1214) WicketTester#startPanel does not
work (correctly)
Posted by Juergen Donnerstag <ju...@gmail.com>.
done
On Sat, Nov 27, 2010 at 6:37 PM, Martin Grigorov <mg...@apache.org> wrote:
> 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)
> <ji...@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.
>>
>>
>
Re: [jira] Resolved: (WICKET-1214) WicketTester#startPanel does not
work (correctly)
Posted by Martin Grigorov <mg...@apache.org>.
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)
<ji...@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.
>
>