Over the years of developing themes we have learnt quite a lot in terms of how to best develop our themes for a wide audience. Things like knowing when to put a feature into a plugin VS baking it into the theme, knowing when to stop adding features just for the heck of it, and finding the best plugins and methods to bug test our themes before release.

Today I just wanted to go over some of the details of how we bug test our themes and do quality assurance testing. I find the best way to bug test a theme is to set it up as if you were going to use the theme yourself for a project. This way you can spot all the difficulties customers could run into and iron out all the kinks.

The number one lesson I’ve learnt over the years is to ask yourself continually the question: “Could this feature be in a plugin?”. We believe the theme should just be the appearance and not the functionality. We have, ourselves, included features in our themes that should have been apart of a plugin and saw how adding the functionality into the theme has caused issues with updates, support, and overall has cost us money. So if you’re a theme developer, ask yourself  “Could this feature be in a plugin?”.

On that note: We have some great upcoming themes in the near future that use our new plugin “Framework” for the functionality and the theme just is, for the most part, a CSS file. We hope that this will help us develop themes much faster as updates can be done to the theme without changing the customizations the customer may have done to the theme.

My top 5 plugins I use when bug testing our themes are:

  1. Monster Widget – this plugin consolidates all of 13 core widgets into one single widget meaning I don’t have to drag all the widgets into the side bar, I can just move the one Monster Widget into the sidebar area, this saves a ton of time and helps us see all the issues that need to be addressed via CSS in the theme.
  2. VIP Scanner – which is very much like the Theme Check plugin but if you’re thinking of submitting your themes to the WordPress.com marketplace then you need to run this plugin against your theme. It has a few different checks built into the plugin i.e. WordPress.com and WordPress.org theme review checks. It allows you to run the checks against themes, plugins, directories, single files etc.
  3. Deprecation Checker – along with running the WP_Debug mode in your WordPress setup, I use this plugin to see any deprecated functions that may be in the theme. It allows you to view all the deprecated functions with the path to the file, which line number the deprecated function is on, and the new recommended function to use.
  4. JetPack – It can cause a ton of issues with the theme so I extensively test our themes with all of the features that JetPack offers. Each time theres a new feature in JetPack I have to test it with the theme
  5. WordPress Beta Tester – testing with future releases of WordPress is something that I haven’t done much of.  But now that I’ve found a plugin that makes it easier, I will be checking our themes with the nightly builds when the WordPress version is close to being released.

So what are some plugins or ways you like to bug test your themes/plugins? If you have any suggestions, I’m all ears!

6 thoughts on “Learn From Our Mistakes, Bug Testing Theme Tips

  1. Pingback: Bug testing theme tips from MintThemes : Post Status

  2. Pingback: 5 WordPress plugins to help with theme debugging - WP Force

Leave a Reply