1. Testing Multimedia Products
DMM

2. Purpose of Testing Testing evaluates the product. Does it work!
Testing can also allow the comparison of alternative prototypes. Is it better than before
Problems found late can be difficult to fix (and much more expensive)

3. Testing for: All applications contain bugs or errors
Spelling ‘muistakes’
Poor grammar – “The game for people is young.”
Factual errors – “Video is interactive”
Functional issues ‘Usability’ – does it work?

4. Basic testing: Usability Acceptance
Does the product function as it should?
Do the graphics, audio, animation and video segments work
Acceptance
Does the product meet the brief?

5. Testing feedback Informal feedback is ‘hit and miss’. It’s nice!
Test within an organised framework
Ask specific questions
Remember: There is no average user. All users differ.

6. Testing Techniques: Walk through – demonstrate the product
Observation – watch the tester use the product
After the tester has used the product:
Questionnaire – a list Multiple choice questions
Interview – feedback in response to set questions

8. Testing stages: Competitive analysis: Exploratory testing:
occurs during feasibility study.
explore user reactions to existing similar products
Exploratory testing:
done early in the design stage
check if the user conceptual model is effective;
General look and feel
usually done either with paper designs or prototypes.

9. Testing methods - analysis
Black Box testing
White box testing
Grey box testing
Functional testing
Non-Functional testing
Usability testing
Performance testing
Security testing
Testing documentation

10. Functional Testing Unit testing: Integration testing: System testing:
show that individual parts are correct in terms of requirements and functionality
Integration testing:
testing of combined parts of an product
System testing:
testing the system as a whole
Regression testing:
verify that a fixed bug hasn't resulted in another bug elsewhere

11. Alpha testing
The product is evaluated relatively early in the development phase
Purpose is to review the application concept
The main focus in alpha testing is to look at:
format
user interface
page layouts
Some content or functionality might be missing

12. Beta testing Product is evaluated just prior to final release
Product should be relatively bug free and complete.
Beta testing is to find bugs and content mistakes.

13. Testing - participants
Use people representative of that target user group
Recruit strangers not friends.
Friends may be inclined to withhold information that may 'hurt the tester's feelings'.
Note: Ensure that the test participant (or Guardian) signs a 'Consent Agreement'. This is especially important if the test session is being videotaped.

14. Summative evaluation
After the authoring (at stages through production - not just at the end).
All requirements are checked – have they been met
Storyboards are compared to the product - does it match the specified design

15. Formative evaluation
Formative evaluation is in-process evaluation that makes sure the product does what is was ordered and supposed to do.
It starts from the moment storyboards and requirements activities begin.