On Thu, Mar 26, 2009 at 2:59 PM, Ovid <publiustemp-perl...@yahoo.com> wrote: > That's the main reason why our tests don't run on production right now. I > would like, at the very least, to have a './Build sanity' target to ensure > that guaranteed non-destructive tests are run, but the strange argument I'm > facing is that "production should be an exact copy of staging and thus tests > on staging should be enough". > > The word "should" makes my trigger finger itch.
So test the assertion that production is an exact copy of staging. E.g. md5sum of a manifest of files. If there's a concern about processor load, use a cheaper checksum and bump up if there is a collision. Or handle it via process -- who's on the hook if the assertion fails and make them sign something affirming it. Pass the buck. :-) -- David
