Test script with hierarchy

2007-02-01 Thread Gabor Szabo
hi, In a project I am working on there is a separate automation team. This team gets test descriptions from the manual QA people including steps how to implement each step: Test A Step 1 - Setup a smadge and set it to operation Blue Step 2 - Setup another smadge and set it to operation Black

Module Announcement: Perl-Critic-1.01

2007-02-01 Thread Jeffrey Thalhammer
After more than 18 months of development, Perl-Critic has reached its first major release! Version 1.01 is now available on a CPAN mirror near you. For those of you who aren't familiar with it, Perl-Critic is a highly flexible static source code analyzer

Re: Bad test functions in Test::Exception

2007-02-01 Thread chromatic
On Thursday 01 February 2007 13:37, Joshua ben Jore wrote: > I'd be a happy guy if a paranoid T::E caused consternation and people > to post "OMG! My stuff fails now!" to perlmonks or whatever. Be very careful with that. I fixed a bug in Test::MockObject a while back and a few people yelled ver

Re: Bad test functions in Test::Exception

2007-02-01 Thread Nadim Khemir
On Thursday 01 February 2007 22:37, Joshua ben Jore wrote: > I'd be a happy guy if a paranoid T::E caused consternation and people > to post "OMG! My stuff fails now!" to perlmonks or whatever. I use T::E extensively and I, too, would like to see a complete paranoid module. Someone wrote, "don'

Re: Bad test functions in Test::Exception

2007-02-01 Thread Joshua ben Jore
On 2/1/07, Adrian Howard <[EMAIL PROTECTED]> wrote: On 1 Feb 2007, at 16:28, Joshua ben Jore wrote: [snip] > There's is nothing special about what T::E is doing to detect errors - > it just turns out the popular practice of looking at $@ is flawed. > That's a problem with the pattern and I expect

Re: Bad test functions in Test::Exception

2007-02-01 Thread Adrian Howard
On 1 Feb 2007, at 16:28, Joshua ben Jore wrote: [snip] There's is nothing special about what T::E is doing to detect errors - it just turns out the popular practice of looking at $@ is flawed. That's a problem with the pattern and I expect that what it means is that if T::E starts detecting error

Re: Bad test functions in Test::Exception

2007-02-01 Thread Joshua ben Jore
On 2/1/07, Adrian Howard <[EMAIL PROTECTED]> wrote: On 31 Jan 2007, at 16:42, Joshua ben Jore wrote: [snip] >>dies_ok { $o->annoying_corner_case } 'exception thrown'; >> >> do the SIG{__DIE__} dance make the tester write >> >>dies_ok { $o->annoying_corner_case; 1 } 'exception thrown'; >

Re: Bad test functions in Test::Exception

2007-02-01 Thread Adrian Howard
On 31 Jan 2007, at 16:42, Joshua ben Jore wrote: [snip] dies_ok { $o->annoying_corner_case } 'exception thrown'; do the SIG{__DIE__} dance make the tester write dies_ok { $o->annoying_corner_case; 1 } 'exception thrown'; If the SIG{__DIE__} dance happens entirely in T::E (as I suggeste