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 2013/06/25 14:20:21 UTC
[jira] [Resolved] (WICKET-4585) WicketTester.assertErrorMessages
passes even if the message isn't visible on the page
[ https://issues.apache.org/jira/browse/WICKET-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-4585.
-------------------------------------
Resolution: Fixed
Added org.apache.wicket.util.tester.WicketTester#assertFeedbackMessages(IFeedbackMessageFilter, Serializable...).
Now the application code can use any filter to decide whether to look for renderer or not messages, their level, etc.
> WicketTester.assertErrorMessages passes even if the message isn't visible on the page
> -------------------------------------------------------------------------------------
>
> Key: WICKET-4585
> URL: https://issues.apache.org/jira/browse/WICKET-4585
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.6
> Reporter: Trejkaz
> Assignee: Martin Grigorov
> Fix For: 7.0.0
>
>
> If you forget to add a FeedbackPanel to the page, WicketTester.assertErrorMessages will still pass the check even though no error message was actually displayed to the user. This makes it essentially unusable as a meaningful test (I am using assertContains for the time being.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira