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!
![CSS Gradients]()
With CSS border-radius, I showed you how CSS can bridge the gap between design and development by adding rounded corners to elements. CSS gradients are another step in that direction. Now that CSS gradients are supported in Internet Explorer 8+, Firefox, Safari, and Chrome...
![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...
![Google Extension Effect with CSS or jQuery or MooTools JavaScript]()
Both of the two great browser vendors, Google and Mozilla, have Extensions pages that utilize simple but classy animation effects to enhance the page. One of the extensions used by Google is a basic margin-top animation to switch between two panes: a graphic pane...
![CSS Tooltips]()
We all know that you can make shapes with CSS and a single HTML element, as I've covered in my CSS Triangles and CSS Circles posts. Triangles and circles are fairly simply though, so as CSS advances, we need to stretch the boundaries...
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.