in reply to Parallel maintenance on many projects, part II: The Testing

Any reason you are not using the Test::Harness prove command? For my automated nightly tests, I use a very simple script that runs the prove command against a bunch of directories.
  • Comment on Re: Parallel maintenance on many projects, part II: The Testing

Replies are listed 'Best First'.
Re^2: Parallel maintenance on many projects, part II: The Testing
by brian_d_foy (Abbot) on Sep 27, 2004 at 01:28 UTC

    I tried prove(1) a long time ago. It didn't work right for me, so I didn't look at it again. Andy probably fixed whatever it was, but even if it worked, it doesn't do much for me. It's' probably more useful and valuable to people who haven't developed a testing process that works for them.

    Almost everything prove(1) does I can do with `make test` and some command line magic, since it's basically a shorter way of typing a lot of things. It can run tests in random order, but who's writing tests that depend on each other? (That's what it's supposed to catch, I think ;)

    I want to get the numbers into variables so I can do something with them, such as shove them into a database. With something more fancy, I should only see interesting output (things that need attention) and I should be able to see historical reports. External programs like prove(1) aren't good for that sort of thing.

    --
    brian d foy <bdfoy@cpan.org>