Patch Test Group
What are my fellow ninjas doing to make sure they have good testing for patches. It makes sense to use a sampling of production machines. How do you go about choosing which machines and how many to add to your testing group.
Please log in to answer
Posted by: SMal.tmcc 6 years ago
Posted by: MacDude 6 years ago
With regard to picking out the individual machines used for testing, it is going to be one or more manual labels.
You want a cross section of your environment and you want to use users who will give you feedback.
- Representing different Operating Systems (OS X 10.8, OS X 10.9, Win 7, Win 7x64, etc.)
- Representing different Job Functions (Engineering, Finance, Shipping, Instructors, Labs, etc.)
- IT folks are not very good test subjects; they tend to fix problems rather than reporting them and they don't use the same tools as some of your end users.
- Instead find your 'whiney' users; the ones who call you anytime something isn't right with their world.
Communication is key. Give the users a path to report when something isn't right. Let them know when you will be patching and let them know that they are in the 'advance' group who get 'upgrades' early.
It is possible to have several Labels (e.g. Server Patch Testing, Instructor Patch Testing, etc.)
Test them against a few machine before you roll the patch to a lot of machines. It's much easier to clean up the mess that way.