[
https://issues.apache.org/jira/browse/WICKET-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032300#comment-13032300
]
manthos commented on WICKET-3670:
---------------------------------
Side note:
There are startComponentInPage(componentClass) witch just calls
startComponentInPage(componentClass, pageMarkup) with pageMarkup == null.
Could you please provide same for startComponentInPage(component, pageMarkup)?
Like...
public final <C extends Component> C startComponentInPage(final C
component) {
return startComponentInPage(component, null);
}
> WicketTester does not support custom pages for component testing using the
> new API
> ----------------------------------------------------------------------------------
>
> Key: WICKET-3670
> URL: https://issues.apache.org/jira/browse/WICKET-3670
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.5-RC3
> Reporter: Emond Papegaaij
> Assignee: Martin Grigorov
> Attachments: wickettester.diff
>
>
> The methods to test components only allow custom markup, no custom pages. We
> need custom pages for our testcases. I'll attach a patch to add support for
> this.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
