Greets,

I'm looking to set up a smoke testing regime for one of my CPAN distros. I imagine that it could take the form of a script that performs the following sequence of actions:

• Download a "latest" nightly tarball from a fixed URL.
• Unpack the tarball, build the module and run the test suite.
• Optional: run an additional script which runs each test file under valgrind (with a debugging Perl), screen-scraping valgrind's output to determine whether any memory leaks or errors occurred. (The distro in question uses XS, and this step is actually the primary motivation for setting up smoke tests.)
• If any step fails, send an email report to e.g. mydistro-smoke@example.com.

That seems straightforward enough, but I wonder: has anyone solved this same problem in another way? I can imagine extending the regime, e.g. to provide benchmarking data.