broken unit tests for Wicket 2.0

[Eelco Hillenius <ee...@gmail.com>]

Could someone please take a look at what's wrong with Wicket 2.0's
unit tests? Besides the fact that we have 5 failures and 2 errors,
they generate an enormous amount of serialization errors.

Eelco

Re: broken unit tests for Wicket 2.0

[Juergen Donnerstag <ju...@gmail.com>]

There are two test suites hows features have not yet been fixed in 2.0
- scoped component resolution
- wicket:component tag

I don't know about the others. I can only stress again and again and
again that every one should run the junit tests before committing
anything to make sure the change does not break any code.

Juergen

On 11/27/06, Eelco Hillenius <ee...@gmail.com> wrote:
> Could someone please take a look at what's wrong with Wicket 2.0's
> unit tests? Besides the fact that we have 5 failures and 2 errors,
> they generate an enormous amount of serialization errors.
>
> Eelco
>