3 ms·
When done intentionally. I've seen lots of tests 'escape' their environment for a bunch of reasons (tests got sent to production with a deploy, human was on th
by noir_lord 9y ago
When done intentionally.
I've seen lots of tests 'escape' their environment for a bunch of reasons (tests got sent to production with a deploy, human was on the wrong machine and ran a manual test command etc etc).
It's almost impossible not to screw up at some point, I try to focus on minimising the small mistakes (airline pilots have commented that it's not the first problem that kills you it's the second one).
- ethbro 9y agoThat's why artificially differentiated steps are critical. If the "deploy to test" procedure looks exactly like the "deploy to prod" procedure, except with different servers, then you're asking for human error. Ensure the test deploy procedure will always fail if run against prod targets when half-asleep. Whether it's something like requiring a different config setting or a reload or an account switch. Anything that breaks the process-as-usual.