Pieter Degraeuwe wrote:
>
> ah, ok. I didn't notice that.
>
> Any idea how to that javascript condition should look like in a general
> way?
> (Is there some wichet hook available for this?)
> I'm looking for a generic approach; I don't want to clutter my tests with
> code like "wait until component contains value x, etc.)
>
The javascript condition is usually testing for existence of some HTML
element
changed by AJAX and is identified by an XPath like:
selenium.waitForCondition("selenium.isElementPresent('//some-eleme...@some-attr=\"foo\"')");
In my view, this is part of the test: it is part of the expected behavior
that
is specific to the function concerned.
-----
--
Kent Tong
Better way to unit test Wicket pages (http://wicketpagetest.sourceforge.net)
Books on CXF, Axis2, Wicket, JSF (http://http://agileskills2.org)
--
View this message in context:
http://old.nabble.com/Re%3A-Testing-AjaxSubmitLink-onSubmit%28%29-with-WicketTester-%40L-tp26947384p26955427.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
