Thanks for the link!
This is really interesting and I think I will adapt this.
Unfortunately I am not sure if this addresses my original Problem.
What I need is a kind of code, like this:
// start page...
tester.startComponentInPage(MyFormPanel.....)
// verify that after initial page rendering, the selected item in the
DropDown equals the pageModel's
assertEquals(pageModel.myChoice.getLabel(),getDropDownChoice().currentlyRenderedSelectedChoiceItem());
As described before, I had a problem in the equals. This resulted in
myChoice being let's say "red" and the DropDown containing "red" "black"
"blue", but "please select" was rendered in the DDC, because myChoice("red")
was not equal to dropChoice("red").
Sorry for the pseudo code :-)
So the DDC could not find out that the "red" of my model was the same as the
"red" in the choices list.
Of course this would be a stupid bug, but i would like to protect my code
against fellows changing the equals behavior.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Question-about-unit-testing-tp4651766p4651768.html
Sent from the Users forum 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
