Development processes - testing & evaluation

I don't think I am alone in admitting that I have never tested a print, multimedia, video or web project that was problem free the first time round. Prototypes must be thoroughly before showing to a client and re-tested following any debugging and changes before publishing.

Alpha testing

Alpha testing should be carried out constantly through the authoring process within the development group.

When the prototype is complete, test it on the widest possible range of systems including ...

  • desktop and laptop Macs
  • desktop and laptop PCs
  • mobile devices
  • iPad's and tablets
  • games consoles
  • media systems
  • etc

Beta testing

This involves recruiting a variety of real world end-users, asking them to test and then submit a questionnaires. You can create a web form for them to complete and submit.

The problems encountered will inform a further process of refinement and debugging.

Testing plan

The following is a suggested plan for testing a web site functions correctly for identified end-users before it is published to the public. Testing should be carried out at identified test sites by typical end-users.

1) Upload the project to a testing server.

2) Test the project on the following devices ...

  • iPhone
  • Blackberry
  • Android
  • Windows 7 Phone
  • iPad

3) Test the following operating systems ...

  • Windows XP/Vista/7
  • Mac OSX and iOS

4) Test with the following browsers (all recent versions, last 2 years?) on PCs and Macs ...

  • Firefox
  • Safari
  • Chrome
  • Internet Explorer
  • Opera

5) Test with required browser plug ins for the project

6) Test on differing Internet connections ...

  • dial-up
  • broadband
  • intranet
  • wi-fi
  • 3G
  • EDGE

7) Test audio - Soundcard, speaker, headphones

8) Test with mouse, trackball, touch screen.

9) If problems are found, analyse, debug, re-publish and retest.

Debugging

To be completed by interface and back-end designers.