[prev] [thread] [next] [lurker] [Date index for 2002/09/09]
On Mon, Sep 09, 2002 at 08:17:23AM +0100, Simon Wistow wrote: > You know those times when you write some code and then spend the whole > day trying to debug it and then, 2 minutes after you've flopped, > frustrated and irritated into bed you suddenly have a moment of > ephiphany and realise that it's the tests that are wrong and not the > code? I'm actually going to argue that you shouldn't be able to do that if the api you're testing is sane. I've just tried to debug the new failures[0] you added to the tests for the Plugins but can't keep the api for Storage->config and Plugin->config straight in my head. There's something about 4 positional parameters that need to be '' rather than undef for falseness that twists my noodle, and I can't shake the feeling that potential third-party Plugin authors won't get it either. I'm going to eat some pie now, after which I'll see if I can't find some way to make this suck less. [0] Failed Test Stat Wstat Total Fail Failed List of Failed ------------------------------------------------------------------------------- t/10plugin_replyto.t 255 65280 5 4 80.00% 2-5 t/10plugin_simplesig.t 255 65280 2 2 100.00% 1-2 Failed 2/13 test scripts, 84.62% okay. 6/203 subtests failed, 97.04% okay. -- Richard Clamp <richardc@xxxxxxxxx.xxx>
Generated at 13:56 on 01 Jul 2004 by mariachi 0.52