Testing Takes Time After An Update
The main problem of using Open Source solutions like WordPress and other CMSs is that you are basically using someone else's code. This means having a lot of faith that their code won't give you any problems. This seems too much of an expectation as most of us don't even have faith in our own code. ;D
So anyway, the recent WordPress and WooCommerce updates got me thinking about one thing... testing. Because of the WordPress core upgrade and the wrong impression people got from going from 3.9 to 4.0, a lot of WordPress administrators really got worried that something bad would happen. (This is harkens back to the 2.9 to 3.0 WordPress update that broke a lot of sites). But there was not a lot of significant changes IMHO. It was like upgrading from 3.8 to 3.9.
Add to that the WooCommerce upgrade that was actually a Major update. Now what you should expect from core updates to either WordPress or Popular plugins is the fact that there will be minor updates from plugins and themes to follow, not counting the patch updates to fix bugs that occur. So this means multiple updates to run.
Now updating is important and ignoring it is just like taking a brick and hammering it on your face. However, after running the update, you are left with a dreaded feeling that "something" might be wrong and the only thing that can satisfy that feeling is to test the entire site.
This means testing the links, looking at the markup and layout, testing the widgets, additional features. etc. If you use WooCommerce, this means keeping track of all the functionality you've added and testing those. Not to mention testing all the active WooCommerce features that you've implemented. All of these takes time.
In fact for one site, I finished the updates on my testing server in only 30 minutes. But testing took me the better part of 3 hours. Going through a list of what I worked on the site and checking them one by one. That's the only way I feel secure that the update went well.
How do you test your WordPress sites after an update?