I saw an interesting question pop up last week that I hadn’t seen on The Club before.
does UI automation testing make sense for a CMS? So if we have a website, let’s say medium size business, and they have a CMS where a dozen or so employees manage the website content, adding images, creating pages etc. Now, we are building a new CMS to replace the old. Someone asked me if it makes sense to try UI automation testing, which would obviously be used for maybe some years as an ongoing tool. My first instinct was “no” because the CMS is not continuously developed so they rarely break + cost/value factor as CMS itself is ‘just’ a tool.
So, what do you think? Does UI automation make sense for a CMS?