Re: What I hate about *Unit frameworks.

On 1 May 2013 11:27, Angel Java Lopez <[email protected]> wrote:
> John, usually I don't find the case "this test corrupts that test", and I
> wrote thousands of tests.
>
> Any example/case?

I've seen more of the opposite problem. When previously isolated tests
show up a bug when run together - because there was some state that
should have been reset that wasn't.

A few years back I spent a chunk of time with several organisations
moving Perl test suites that were in a one-test-per-process style to a
shared xUnit style test (mostly coz I wrote the most popular Perl
xUnit framework of the period ;-)

The fear of test cases interfering with each other was something that
was raised before we did the moves - but it turned out to be largely
baseless. I don't have the numbers to hand, but I do remember that we
found many more bugs that had been hidden by separate processes than
problems due to tests interfering with each other.

Cheers,

Adrian
--
http://quietstars.com     [email protected]     twitter.com/adrianh
t. +44 (0)7752 419080     skype adrianjohnhoward     pinboard.in/u:adrianh


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/testdrivendevelopment/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/testdrivendevelopment/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/