Just curious if anyone has run clover or cobertura maven reports against the codebase to see what kind of unit test coverage their currently is. I have *no* doubt that wicket's unit test coverage is *extremely* high compared to other web frameworks, but it might be good to see if there are any important gaps (like this) that need coverage.
>From a community perspective, I know I would be comfortable contributing unit tests to help out. On Dec 2, 2007 6:24 PM, Gerolf Seitz <[EMAIL PROTECTED]> wrote: > hi all, > > there has been an issue, that ajax related unit tests didn't test with an > ajax request, > but rather with a normal request[0]. > as a consequence, the generated markup inside the ajax response was actually > the markup for normal requests > (eg. included wicket tags and wicket attributes, which is not the case for > "real" ajax responses). > > the effect of this change is, that your ajax related unit tests will > probably fail with the current trunk. > i expect that most failed tests can be fixed by correcting the expected ajax > result. > > it's rather unfortunate that this happens so close to the 1.3.0 final > release, but then again it's fortunate > that we caught it before the release at all ;) > > as usual, if there are any questions left unanswered, don't hesitate to > ask/complain/investigate/... > > Regards, > Gerolf > > [0] https://issues.apache.org/jira/browse/WICKET-1199 >
