If you just click the link, both IE Firefox use the file name configured in
response.setAttachmentHeader().
However, if you right-click the link Save Link As..., I found IE uses the
file name configured in response.setAttachmentHeader(), but Firefox uses the
file name part of the href. So
To be honest, there's nothing wicket-specific about it. Testing AJAX is
pretty easy, just use waitFor* assertions to delay until the AJAX component
is loaded.
One slight irritation is that Wicket munges the id of its components, making
element identification a bit tedious, so I eventually wrote
I've been using http://storytestiq.solutionsiq.com/ STiQ for integration
testing on my current project. It's a mashup of Selenium Fitnesse. It
makes for a really comfortable test construction running environment.
I've used JUnit driven Selenium tests in the past, but the tests were
http://www.jroller.com/karthikg/entry/modelling_client_side_form_modifications
http://www.jroller.com/karthikg/entry/modelling_client_side_form_modifications
might be what you're looking for. It works well, but it works best when the
behaviour is attached to the onbeforeunload event, which you
