Stubbing is great, unless you're using a 3rd party library (Swing) which is calling a method (isEnabled) on your mock (Action) that you don't know about, so you spend half a day wondering why your behaviours are all broken and eventually have to look in the 3rd party source code to find out what's going on.
I'd like to change the automatic stubbing so that it defaults when you do mock.stubs(), but otherwise throws a wobbly for unexpected calls. Cheers, Liz. -- Elizabeth Keogh [EMAIL PROTECTED] http://www.livejournal.com/users/sirenian
