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!
![Welcome to My New Office]()
My first professional web development was at a small print shop where I sat in a windowless cubical all day. I suffered that boxed in environment for almost five years before I was able to find a remote job where I worked from home. The first...
![Responsive Images: The Ultimate Guide]()
Chances are that any Web designers using our Ghostlab browser testing app, which allows seamless testing across all devices simultaneously, will have worked with responsive design in some shape or form. And as today's websites and devices become ever more varied, a plethora of responsive images...
![Detect Vendor Prefix with JavaScript]()
Regardless of our position on vendor prefixes, we have to live with them and occasionally use them to make things work. These prefixes can be used in two formats: the CSS format (-moz-, as in -moz-element) and the JS format (navigator.mozApps). The awesome X-Tag project has...
![Truly Responsive Images with responsive-images.js]()
Responsive web design is something you hear a lot about these days. The moment I really started to get into responsive design was a few months ago when I started to realise that 'responsive' is not just about scaling your websites to the size of your...
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.