— Keep your WordPress site steady during changes
Avoid introducing problems when running updates
Updating things in WordPress can seem trivial at first, all you have to do it click Update in the backend and it's all smooth sailing from there on, right?
This is unfortunately not always the case, things can and do go wrong when running updates. This is the main reason why extra precautions like Visual Regression testing and updating on staging version first need to be taken before and during updates.
How can you detect if something has changed on site after updates?
This is a very difficult task if you don't have help by automated tests. You can theoretically 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, and very time-consuming, to keep track of changes manually.
We use Visual Regression Testing to check the front-end, and automated script tests to verify back-end functionality. Read more about these processes below.
— How do we detect visual changes and bugs?
How we compare before and after states visually
— How do we ensure functionality before and after updates?
How automated tests work - example logging into WordPress
— Where do we perform the updates?
We always perform updates on a staging server of the site first.
If everything goes well on the staging site then we can move on to updating the production site.