On Sat, 01 Dec 2007, Per Newgro wrote: > but isn't this cheating? Hmm. I never saw the FeedbackMessageClearing. > I always assumed that my test has to simulate the browser behavior. So i used
Well, I find WicketTester tests to be so white-box that they are pretty far from the actual browser anyway, and find them better for single-component unit tests. Thus I would have fixed the original problem by putting the valid and invalid cases to separate tests methods. WicketTester tests are not purist unit tests as they use the file system (to load the markup files) and parse markup xml which is slowish, but this is not a practical problem before you have thousands of tests. Then it might get slow (over 10 seconds) to run them. Off-topic: if you use feedback messages, I heartily recommend reading _About Face_ by Alan Cooper and checking out Wicket built-in ajax :) Best wishes, Timo -- Timo Rantalaiho Reaktor Innovations Oy <URL: http://www.ri.fi/ > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
