Web and software design are gradually becoming interchangeable

As the capabilities of web-based software expand, the presence of a stringent Quality Assurance Process becomes ever more important. The advantage of Drupal over other forms of web-based software is that these changes can be made quickly and effectively with minimal disruption to the site's users even while the site is live.

We try to reduce the need for such changes once a site is live by following a strict Quality Assurance Process on all our sites and their individual releases. The stages of this process are:

  • Design and Development
  • Internal Quality Assurance
  • External Quality Assurance
  • Go Live

Design and Development

Alltooeasy thoroughly tests the features throughout the process of development. Typical tests may include:

  • User Interface (UI) testing: ensuring that it not only looks good on paper but translates intuitively and effectively to the web
  • Link testing: making sure that A links to B and that the path is natural to the user
  • Debugging: eliminating errors and unexpected results
  • Performance testing: assuring everything on the site renders quickly and efficiently
  • Scalability: creating dummy content to guarantee that the site works for the maximum number of expected users
  • Permissions testing: establishing a hierarchy of permissions stipulates the access control for individual users

Internal Quality Assurance

  • Browser Cross-Compatibility testing: modern browsers render web content differently. By default the site will be tested in the latest stable version of Internet Explorer, Firefox, Chrome and Safari.
  • SPAG: checking all spelling, punctuation and grammar
  • External content: assuring all external content such as video, images and social media feeds display correctly
  • Search engine optimisation: testing internal and external search terms
  • Premium content: preventing unregistered access to premium content. The QA team will try and gain access to this content as unregistered users.

External Quality Assurance

  • Client site testing: clients can access the quality assurance domain. They can add content, report bugs, test security to gain piece of mind ahead of going live.
  • Bugs sent back to the developer and fixed in this release if possible
  • Additional features requested by the client are analysed; an appropriate release date determined and additional quote submitted back to the client
  • Once sign-off is approved a "go live" day is agreed upon and a code freeze is put in place for this release

Go Live

  • If this is the first release the QA database will be migrated into the production server. If not, the existing database will be backed up.
  • Database install-scripts and updates will be applied
  • Site files are uploaded and the site is activated
  • Client notified of all bug fixes and features added during release

You can see our full terms and conditions here.

We also offer a range of support services that complement our QA process, meaning that we can quickly respond to any bugs that emerge post sign-off.

Please contact us for more detail on our QA process or, alternatively, read more about our design and development processes.

You are here

Home