• What tests have you taken or seen?
• What is testing?
• Why bother Testing?
D2
“carry out acceptance
testing with client on an
interactive website”
1. creating a test plan/table
2. functionality (e.g. working internal, external
links, content loads/works)
3. usability (e.g. Meta tags, clear navigation,
viewable in different browsers, ease of use)
4. readability (e.g. proof read, spell checked,
text readable with background colour)
5. accessibility (e.g. ALT tags included,
additional features function)
6. review against original specification
7. W3C Compliance.
1. creating a test plan/table
2. functionality (e.g. working internal, external
links, content loads/works)
3. usability (e.g. Meta tags, clear navigation,
viewable in different browsers, ease of use)
4. readability (e.g. proof read, spell checked,
text readable with background colour)
5. accessibility (e.g. ALT tags included,
additional features function)
6. review against original specification
7. W3C Compliance.
Test
Number
Description
of test
Test
Methods
Expected result
Actual
result
Outcome
1
Hyperlink 1
Home-Page
Click Link
Loads Home
Page
Loads Shop
Link invalid re address the
hyperlink
2
Hyperlink 1
Home-Page
Roller
Changes
colour to red
Hover over
link icon
Changes to red
Changes to
red
None Required
3
Check video
loads and
plays
Click play
function
Play video
Video does
not load and
play
Check embedding code
Save your website as version 2 - to share with the examiner
• Begin the create your test plan on
Word
• Advisable to use A3 landscape
• Make sure any screen shots are clear
• Be systematic and ordered
1. functionality (e.g. working internal,
external links, content loads/works)
1. usability (e.g. Meta tags, clear navigation,
viewable in different browsers, ease of
use)
1. readability (e.g. proof read, spell checked,
text readable with background colour)