The Truth About Production Testing
Testing on production environments is something you must do but really, really would prefer not to do, right? You can do some incredible damage in a short amount of time if you aren't careful, and when things do run smoothly, you think to yourself "Why even take the risk? I should just do this on the staging server and call it a day!" Well, you can't get around automated and manual testing on production, and this image seems to represent what it feels like to do testing on production:
That's the first bulletproof vests being tested ... on a living human being. If you don't see the parallel between that photo and production testing, you don't have a sense of humor. Tread lightly when testing on production, people: you could end up shooting yourself down quickly!
![How to Create a Twitter Card]()
One of my favorite social APIs was the Open Graph API adopted by Facebook. Adding just a few META tags to each page allowed links to my article to be styled and presented the way I wanted them to, giving me a bit of control...
![Responsive and Infinitely Scalable JS Animations]()
Back in late 2012 it was not easy to find open source projects using requestAnimationFrame() - this is the hook that allows Javascript code to synchronize with a web browser's native paint loop. Animations using this method can run at 60 fps and deliver fantastic...
![MooTools Fun with Fx.Shake]()
Adding movement to your website is a great way to attract attention to specific elements that you want users to notice. Of course you could use Flash or an animated GIF to achieve the movement effect but graphics can be difficult to maintain. Enter...
![Fixing sIFR Printing with CSS and MooTools]()
While I'm not a huge sIFR advocate I can understand its allure. A customer recently asked us to implement sIFR on their website but I ran into a problem: the sIFR headings wouldn't print because they were Flash objects. Here's how to fix...
This was a great little warning first thing in the morning. :) Thanks for the joke!
Not sure why they can’t use a pig to test that vest.
Also, if we can run full copy of production server for tests (and with copy of production DB), why not use it? Some external API can’t be copied (so we should consider about mocks instead of real payment gateways), but most “damage” usually goes to our DB, so I think it’s worth it. And it’s relatively cheap, if you use services with per-use payments.
I’ts not advisable to do any testing on a production server. They should be done on the development server. Thanks for this piece.