Approaching a testing project without a proper plan in place is likely to cause problems and create headaches for you later down the line. Why do we test so comprehensively? Because it saves time and more importantly money. With that in mind, whether we are building in Umbraco or WordPress etc, we create a fully comprehensive and customized testing plan for each project we do and we do this using task boards in asana. This may look daunting at first but when you realise it covers just about anything that can go wrong with a site build, it is worth the extra time and the final product will reflect this. If you are known for good, reliable work as an agency or even freelancer, this reputation will pay you back in the future.
Below is a screengrab of our full testing plan on asana, each column is set up as a number of different tasks which are completed and checked off before moving onto the next column.
The first column comprises of Testing specification tasks, this is important information about the project which is gathered and recorded for reference while testing such as CMS logins, key pages and journeys, lists of URL’s, designs and visual references etc. All this information is gathered before testing has started.
After the first column has been completed we move onto the second which is SEO/Performance. This is where we check such things as Redirects, Robots.txt file and run tests such as Screaming frog to check for 301’s, 404’s etc.
The next column is Security. This is where we run Mozilla Observatory, SSL security test and verify the HTTPS certificate of the site.
After this we move onto Design Validation. Here we compare the new site with the site designs and any variation, no matter how seemingly insignificant, is recorded as an issue. We also test based on a list of the most popular used browsers and devices which we update every two months. You can find these lists that are based on business size here. Any extra devices or browsers needed to be tested on are discussed with the client and extra time negotiated to cover this.
Functional testing is next which covers site search, social feeds, user logins, checkout journeys, maps, 404 pages and form submissions.
Finally back office testing, which covers all CMS related functionality such as media libraries, content publishing and errors.
There is another column on the end of this testing regime that we call ‘Improvements’, this is where we record any observations of site aspects we think could be improved either at that time or potentially in the future. These can then be presented to the client for their consideration.
This testing plan has so far proved to be an effective solution to a testing process that we have refined over the years. If you are looking for a solid plan for your testing projects, then you can’t really go wrong by following this formula.
If you are interested in our digital services, including full site testing then get in touch with us by clicking here.