[
https://issues.apache.org/jira/browse/WICKET-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16084185#comment-16084185
]
Kamil edited comment on WICKET-6423 at 7/12/17 3:44 PM:
--------------------------------------------------------
I'm aware of WicketTester#assertComponent(String path, Class expectedType), but
this method takes "path" and I'm starting the component using
"wicketTester.startComponentInPage(panel);" so there is no "path" and
{code}
wicketTester.assertComponent("test", MyPanel.class);
{code}
looks a bit awkward...
But I can agree that this feature request should have low priority
was (Author: eximius):
I'm aware of WicketTester#assertComponent(String path, Class expectedType), but
this method takes "path" and I'm starting the component using
"wicketTester.startComponentInPage(panel);" so there is no "path" and
{code}
wicketTester.assertComponent("test", SelectHospitalPanel.class);
{code}
looks a bit awkward...
But I can agree that this feature request should have low priority
> WicketTester should provide assertRenderedComponent method
> ----------------------------------------------------------
>
> Key: WICKET-6423
> URL: https://issues.apache.org/jira/browse/WICKET-6423
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Reporter: Kamil
>
> When I'm testing Page, I have convenient method to test if it has rendered
> successfuly:
> {code}
> //when
> wicketTester.startPage(MyPage.class);
>
> //then
> wicketTester.assertRenderedPage(MyPage.class);
> {code}
> but when I'm testing particular component:
> {code}
> //given
> final MyPanel panel = new MyPanel("test");
> //when
> wicketTester.startComponentInPage(panel);
> //then
> ??
> {code}
> then I need "assertRenderedComponent(MyPanel.class) in order to test if it
> rendered successfuly
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
