Since [trunk][trunk] went 2.0 there have been an extensive amount of failing unit tests. Many of them is because Wicket 2.0 is going to handle things differently which means some of the tests needs to be rewritten/changed to match the new behaviors. These are actually the hardest tests to fix, because they require some knowhow of the specific test.

Some of the tests fails because the ordering of the attributes when added to a tag from Wicket has changed. So all the diff tests which compares the output generated with a static html file now fails. The solution here is quite simple: Just create new static html files for comparison.

Last there were some tests that failed because you can’t add components to parent, which isn’t backed in a Markup file. Many tests just used a dummy page, with no .html file and therefore no matching wicket:id’s for the components added to that page. The solution for this is to have html files which matches the component tree in the tests. Luckily many of the tests had the exact same component hierachy (namely a Page with one component on it), so it didn’t require a new .html file for every one of them.

Yesterday I [fixed][patch] all the failing tests of the last type. I just hate failing unit tests

[trunk]: http://svn.sourceforge.net/viewcvs.cgi/wicket/trunk/
[patch]: http://svn.sourceforge.net/viewcvs.cgi/wicket?rev=6274&view=rev