Stretch tasks R097 TA3: Testing and Reviewing Interactive Digital Media

Round 1: Quiz Blitz

1. Functionality Functionality testing covers every interactive element.
2. compatibility Screen sizes are part of it too.
3. Before the test is run Otherwise there is nothing to compare against.
4. False No assessor believes a log without failures.
5. A task to complete Then stay quiet and record every hesitation.
6. You already know where everything is You cannot experience being lost in it.
7. Five Five real users find most of the problems.
8. 200 Keyboard only and a screen reader are tested too.
9. Evidence against each requirement; Quoted user feedback, including criticism The review is marked on evidence.
10. How the product could grow beyond the brief New features, content or platforms.
11. Five of six testers finished without help Numbers from real testing are evidence.
12. Performance Large files show up in performance testing.

Round 2: Quick Fire

1. • It is what the actual result is compared against
   • Written afterwards, it would just describe whatever happened
   Model answer

   The expected result, taken from the plan, is what the actual result is compared against. Written afterwards, it would simply describe whatever happened, so every test would appear to pass.

2. • A task shows whether a user can achieve a goal without help
   • Hesitations and wrong taps are the findings
   Model answer

   A task, such as booking two tickets, shows whether a real user can achieve a goal without help. Watching quietly, every hesitation, wrong tap and backtrack is a finding, which a guided tour would hide.

3. • Evidence from testing, such as four of five testers
   • A specific improvement, such as adding a button
   Model answer

   Four of five testers reached the booking screen in under three taps. The fifth looked for a Book button in the top right, where convention puts it, so I would add a persistent booking button to the header.

4. • Criticism reveals weaknesses that lead to improvements
   • Praise alone is not believable, as reviews are marked on evidence
   Model answer

   Criticism reveals the weaknesses that lead to specific improvements, which is what the review is for. A review that only praises the product is not believable, because the review is marked on honest evidence.

Round 3: Big Think

1. • Functionality: every button, link and the form
   • Navigation: every screen reachable, no dead ends
   • Content: spelling and everything in the brief
   • Compatibility: browsers and devices
   • Accessibility: keyboard, screen reader and 200% text
   • Performance on a slow connection
   • Each test logged with data, expected and actual results
   • Failures fixed and retested, plus usability testing
   Model answer

   Functionality tests would check every button, link and the donation form, including validation of card details. Navigation tests would confirm every screen is reachable with a route back and no dead ends, and content tests would check the spelling and that everything in the brief is present. Compatibility tests would try different browsers and devices, including phones, and accessibility tests would use keyboard only, a screen reader and text resized to 200%. A performance test would time loading on a slow connection. Each test would be logged with its number, the data or action, the expected result written beforehand, the actual result and the action taken, with failures fixed and retested. Finally, usability testing would watch real users try to donate.

2. • Requirement by requirement, with evidence
   • Quoted feedback, including criticism
   • Strengths and weaknesses, with reasons
   • Specific improvements: how, and with what effect
   • Further development beyond the brief
   • Reflection on the process
   • Evidence rather than opinion
   • A conclusion valuing honesty
   Model answer

   The student should go through the brief requirement by requirement, giving evidence of where each is met, such as a screenshot or a test result. They should quote feedback from the client and testers, including the criticism, and explain the strengths and weaknesses with reasons. Each improvement should be specific, saying how it would be implemented and what effect it would have, and further development should suggest how the product could grow beyond the brief, such as new features or platforms. They should reflect on the process, saying what they would do differently next time. Every claim needs evidence rather than opinion: five of six testers finishing without help proves more than calling it easy to use. Overall, an honest review that improves things scores far higher than one that praises everything.

This or That

1. Compatibility Different browsers and devices are compatibility testing.
2. Usability A real user attempting a task is usability testing.
3. Watching others You know where everything is, so you cannot experience being lost.
4. Opinion Evidence would be how many testers succeeded without help.
5. Record it with the fix A log with no failures is not believable.
6. Further development Growing the product beyond the brief is further development.
7. Stay quiet and note it The hesitations are the findings.
8. No: say what, how and why A strong improvement says what, how it would be done and the effect.

Memory Match

• A 3 Functionality testing: Every element behaves as intended
• B 5 Usability testing: Watching a real user attempt a task
• C 2 Compatibility testing: Different browsers and devices
• D 6 Test plan: Each test, its data and expected result
• E 4 Further development: Growing the product beyond the brief
• F 1 Iteration: Repeated cycles of build, test and refine

Sort It

1. Compatibility Works in Chrome and Safari Different browsers is compatibility.
2. Functionality Every button opens the right screen Checking each element works is functionality.
3. Functionality The quiz adds up the score correctly Correct behaviour is functionality.
4. Usability Watching where a tester hesitates Hesitations are usability findings.
5. Functionality The contact form sends Forms working is functionality.
6. Accessibility Every control works by keyboard Keyboard access is accessibility.
7. Accessibility A screen reader reads the alt text Screen reader support is accessibility.
8. Accessibility Text still fits at 200% Resized text is an accessibility test.
9. Compatibility Works on a tablet in landscape Devices and orientations are compatibility.
10. Usability A visitor books tickets without help A real user completing a task is usability.
11. Compatibility Works on a small phone screen Screen sizes are compatibility.
12. Usability Counting wrong taps during a task Wrong taps reveal usability problems.