Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

BooK (2612)

BooK
  {book} {at} {cpan.org}
http://paris.mongueurs.net/
Yahoo! ID: philippe_bruhat (Add User, Send Message)

Obfuscation [plover.com]. Pink [axis-of-aevil.net]. HTTP::Proxy [cpan.org]. YEF [yapceurope.org]. Fishnet [perl.org]. Kapow [cpan.org]. Cog's [perl.org] bitch [cpan.org]. Invitation [perl.org]. White [perl.org] Camel [perl.org]. Nuff' said.

Journal of BooK (2612)

Tuesday January 25, 2005
06:20 AM

svn test integration

[ #22873 ]

I'd like to set up a svn repository so that the test suite is run after each commit. I'm sure there's a way to do it, I just didn't find out how while skimming over the SVN documentation.

Or maybe I could just a write a script that steps over the release numbers, running 'Build test' until it reaches HEAD. No need for integration, just a cronjob.

We would stick the test result information in some manner of database (along with coverage info). And then I'll start screaming "BAD PROGRAMMER, NO COOKIE!" when someone commits bad code (or tests). :-)

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Inside the directory of your SVN repository is a directory called hooks/, specifically named executable files in here will get run by SVN at various points of your commit cycle. You could easily use this to run your tests with.

    The most common usage of this is to email commital information to a mailing list. At my work, we actually use it to refresh the working copy in our web directory each time we commit (sort of like version controlled FTP). You can read about this stuff in the online version of the SV

    --
    -stvn