We have someone arguing that when our Perl apps move from staging to production, we must not run "make test" because:
1. It's guaranteed to be 'bit-by-bit' identical to staging. 2. Downtime must be minimized and we can't waste CPU or I/O on "make test". These are often heavily loaded boxes and downtime really is a crucial issue. For those of you in large environments, do you run "make test" or an equivalent when you push your code out to a production server? Why or why not? Cheers, Ovid -- Buy the book - http://www.oreilly.com/catalog/perlhks/ Tech blog - http://use.perl.org/~Ovid/journal/ Twitter - http://twitter.com/OvidPerl Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
