Hallo Sebastien,
I run into a couple of issues when tryting to use WicketTester to write
tests on classes and forms the are created using Wicket jQuery UI.
WicketTester actually expects you to know the component id of an element.
Some of the Buttons will generate those automatically. It does not
Hi Sebastian, i am currently on vacation. I am coming back to you end of
next week!..
Thanks & best regards,
Sebastien
On 13 sept. 2013, at 22:04, "seba.wag...@gmail.com"
wrote:
Hallo Sebastien,
I run into a couple of issues when tryting to use WicketTester to write
tests on classes and form
Hi Sebastian,
Back on this topic...
I strongly guess you are talking about dialog's button... You are right,
their ids are automatically generated. The reason why the ids are generated
is because DialogButton(s) are actually *not* wicket components, there are
really related to the jquery ui's dia
Hi Sebastien,
well after testing a while with WicketTester I have to admit that writing
test cases with it is quite difficult.
What we want to do with UI testing is really simulating end users. And with
WicketTester you can not really see or debug the test.
I think we will give a try now with Sele
