On Fri, Mar 24, 2017 at 7:58 PM, Maxim Solodovnik <[email protected]> wrote: > In one of our projects I did Wicket 1.4 -> Wicket6 jump :) > Not that scared :)
I tried 1.5 to 6.x a couple years ago, and after doing all the code changes, almost every test failed due to Wicket calling our code a different number of times when doing the same operations, which of course breaks if you're using mocks which expect a certain number of calls. And at the time, I couldn't figure out which calls were legit and which ones weren't, and why it was calling the same thing more than once for a single operation, and ultimately ended up delaying the whole upgrade effort until I had a better reason to upgrade later. So now I have that reason to upgrade, but I'm trying to do it step by step so that I can attempt to reason about any changes of that sort release by release, instead of having to look at a gigantic number of changelogs. And incidentally, whatever the issue was, because it isn't mentioned in the changelog, was fixed in 6.22.0. 6.21.0 fails, 6.22.0 passes - but I don't see any changes in WicketTester. And the code in BaseWicketTester which I thought was passing in the empty parameters still seems to be doing that in the later version, even though the test passes. So it's all very confusing. TX --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
