the testing process

functionality testing

The functionality of your product needs to be rigorously tested in such areas as:

  • installation/uninstallation
  • navigation/hyperlinks/hotspots
  • audio/video/animation operation
  • missing content
  • quizzes/user tracking
  • print/save functionality
  • third-party functionality (e.g. Flash/Word/Acrobat documents)

This can also include testing against a design document or interactive script, and normally takes place on one key platform of the required environment.

Remember, users don't always do what's expected of them.

Expect the unexpected

Complement a rigorous functionality test with 'exploratory' or 'destructive' testing that aims to 'break' your program in unforeseen ways.

You'll then be confident that your product will withstand unexpected user actions.