On 8/2/07, Scott McWhirter <[EMAIL PROTECTED]> wrote: > > On 8/2/07, nadim khemir <[EMAIL PROTECTED]> wrote: > > On Tuesday 19 June 2007 17:52, Mike Malony wrote: > > > So I'm working my project, and I've got one other more junior coder > with > > > me. > > > > > > Has anyone tried writing test files as part of their spec's? > > > > > > An overview document would also be needed, and some time walking > through > > > the expected testing. But it sure would be setting clear > expectations. > > > > That's why I wrote POD::Tested. I needed a tool that would allow me to > sit > > with a "customer" and we'd write the documentation and peper it with > > acceptance test. Then I'd use the document as a test, directly. > > > > Play with it and tell me if you need more. > > > > Cheers, Nadim. > > > > We've been doing this with FitNesse so that our customer can edit > these things directly themselves. I also wrote Test::FITesque to port > some of this stuff so that we can more easily reuse our acceptance > tests for a regression suite. > > We've been using FitNesse with the perl server and writing our own > fixture classes which use WWW::Selenium in the background, it's > similar to SocialText's WikiTest stuff. > > ta! > > > -- > -Scott- >
And now I have two more modules to investigate. Thanks! And thanks to all, I appreciate all the comments. I'm still fighting to build more testing into the process. And I can see several options now that I'd never thought through myself. Mike
