Keep your WordPress site steady on updates - detect errors before your users do
Updating plugins, themes and WordPress
This task can seem trivial at first, all you have to do it click Update on the backend and it's all smooth sailing from there on, right?
Well yes, in a perfect world that would be the case. But like everything else, things go can go wrong when updating things in your WordPress installation. If you've read this far, you're likely keen on keeping your updates headaches to a minimum. Keep on reading and we'll let you know how to do that.
How do you know if something has changed on your website after an update?
The short answer to that question is: you don't.
You can check the site manually, but even on a small site it can be difficult to remember exactly how things looked and functioned before the update. On medium and large sized sites, it becomes more or less impossible to keep track of changes manually.
Automated tests are needed to check if something changed either its appearance or functionality. We use Visual Regression Testing to check the front end, and script tests to verify back end functionality.
How do we detect changes on the front end?
How do we ensure functionality before and after updates?
Where do we perform the updates?
We always perform updates on a staging server or ghost copy of the site first.
If everything goes well on the staging server or ghost copy, then we can move on to updating the production site.