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!
![Detect DOM Node Insertions with JavaScript and CSS Animations]()
I work with an awesome cast of developers at Mozilla, and one of them in Daniel Buchner. Daniel's shared with me an awesome strategy for detecting when nodes have been injected into a parent node without using the deprecated DOM Events API.
![CSS Filters]()
CSS filter support recently landed within WebKit nightlies. CSS filters provide a method for modifying the rendering of a basic DOM element, image, or video. CSS filters allow for blurring, warping, and modifying the color intensity of elements. Let's have...
![MooTools Font-Size Scroller with Cookie Save]()
Providing users as many preferences as possible always puts a smile on the user's face. One of those important preferences is font size. I can see fine but the next guy may have difficulty with the font size I choose. That's why...
![Create a Sheen Logo Effect with CSS]()
I was inspired when I first saw Addy Osmani's original ShineTime blog post. The hover sheen effect is simple but awesome. When I started my blog redesign, I really wanted to use a sheen effect with my logo. Using two HTML elements and...
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.