‘Must Test’ Checklist for Your Drupal Site


2 m read


Web Application Testing

drupal checklistWhile writing a Drupal site, you should ensure you’ve tested it carefully before turning your product over to the client. In case the customer discovers any significant issue, it can degrade their trust as well as cost sales if that problem alone is enough to block visitors’ on-site interaction ability. As you can see, quality assurance testing is really very important.

Thus, consider the following checklist of items you should test on your Drupal website before going live.

Before launch

  • If comments are enabled on the site, the ‘Privacy policy’ link should be there, too.
  • 404 and 403 should display the appropriate information and be appropriately customized.
  • As for Content Type settings in Drupal, turn off preview, ensure revisions are enabled for all types of content and the proper menu is available.
  • Xmlsitemap should be configured and properly updating when content changes.
  • Pathauto patterns should be set appropriately for every content type.
  • Meta descriptions, or titles, should be in place and also available either for views and home page or normal content pages.
  • Client should have enough but not too many permissions, based on the ongoing support with your client.
  • Robots.txt file should correctly block the nodes that are not to be indexed like sidebar block promos, rotators, etc.
  • If it’s not a community website, only admins should be able to create accounts.
  • User passwords should be set to some strong passwords before the launch.
  • Test content should be removed.
  • Google Analytics should be in place and properly working. You may use the real time function in order to make sure anonymous users are also tracking.  If desired, block your client and IP.
  • Development and all unused modules should be disabled.
  • Before testing site appropriate JS and CSS aggregation should be enabled.
  • Drupal cache should be turned on unless using Varnish.
  • Error log should be checked and issues resolved.
  • If you like, make error reporting NOT show on the screen for the production sites and write to log.
  • Site search should work and be themed properly.

Finishing touches

  • All Drupal caches should be cleared.
  • Run the broken link checker and make sure your production site doesn’t have any broken links. Try the module Link Checker.
  • All staging and dev url paths should be set to production. To catch these, use Pathologic.

There can be many more items on your production QA testing checklist. These items are just the major things you should check for your Drupal sites besides browser testing, SEO and lots of other aspects involved in launching your website.

Realizing the importance of providing service on agreed terms, we consider all possible risks and provide efficient solutions for all possible risks and provide efficient solutions.


We use cookies to ensure your best experience. By continuing to browse this site, you accept the use of cookies and "third-party" cookies. For more information or to refuse consent to some cookies, please see our Privacy Policy and Cookie Policy