[WICKET-545] Improve check for components added to AJAX response in WicketTester

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.6, 1.3.0-beta1
• Fix Version/s: 1.3.0-final
• Component/s: wicket
• Assignee: Unassigned
• Reporter: Jordi Salvat i Alabart
• Created: 09/May/07 03:13
• Updated: 16/Sep/08 20:32
• Resolved: 16/Dec/07 01:18

Description

The javadoc for wicket.util.tester.WicketTester.assertComponentOnAjaxResponse makes this statement:

"This method doesn't actually insert the component in the client DOM tree, using javascript. But it shouldn't be needed because you have to trust that the Wicket Ajax Javascript just works."

Turns out that there is another way to have the component replacement fail, which is to forget to setOutputMarkupId(true) or to setVisible(false).

I propose to improve this method to at least check that the component's markup id made it into the page, or at least that the component isOutputMarkupId and isVisible.