1. Testing evaluates the product.

Does it work!

2. Testing can also allow the comparison of

alternative prototypes.
Is it better than before

3. Problems found late can be difficult to fix

(and much more expensive)
All applications contain bugs or errors

1. Spelling ‘muistakes’

2. Poor grammar – “The game for people is young.”

3. Factual errors – “Video is interactive”

4. Functional issues ‘Usability’ – does it work?

 Usability
◦ Does the product function as it should?

◦ Do the graphics, audio, animation

and video segments work

 Acceptance
◦ Does the product meet the brief?
 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.
 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

 Black Box testing
 White box testing
 Grey box testing
 Functional testing
 Non-Functional testing
 Usability testing
 Performance testing
 Security testing
 Testing documentation
 Unit 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
◦ 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
 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.

 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.
 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
 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.