Purpose

Acceptance testing asks whether the product satisfies agreed user/business outcomes. Integrity testing checks whether the complete system behaves coherently end to end—including navigation, data, performance, error handling, recovery and integrations.

The Week 11 exercise uses a peer/mentor unfamiliar with the build. That unfamiliarity is evidence: if they cannot find a call to action or understand the next step without coaching, the design has failed to communicate.

Test protocol

1. Prepare, but do not script the solution

   • Current build/version and environment.
   • Test personas and realistic data.
   • Acceptance conditions from Iterations 1–3 in a simple test table.
   • Critical task scenarios and starting points.
2. Brief neutrally

   • State the goal, not the clicks.
   • Do not demonstrate the path first.
3. Observe silently

   • Where do they pause, backtrack, misread or miss the call to action?
   • What do they expect to happen?
   • Which labels, charts or controls are ignored?
4. Record

   • Scenario, behaviour, expected/actual result, evidence, severity and impact.
5. Decide

   • Fix / defer / reject, with rationale and owner.
6. Retest

   • Verify the fix with the same or equivalent scenario before Expo.

End-to-end coverage

• navigation and every critical call to action;
• valid, invalid and boundary input;
• search, filters, forms and error messages;
• data creation/update/retrieval and integrity;
• APIs/integrations, permissions and session state;
• performance/response time;
• backup, restore and recovery;
• accessibility and understandable visualisations;
• first-time user journey from entry to outcome.

Evidence table fields

• Test ID / date / build:
• Persona and scenario:
• Acceptance criterion:
• Observer:
• Expected result:
• Actual behaviour/result:
• Evidence link:
• Severity / impact:
• Action and owner:
• Retest result:
• Decision rationale:

Important course note

The video’s spoken weekday references may reflect an earlier delivery. Use the current S2 2026 Moodle section for deadlines: Build Monday 12 Oct 11:55 PM; Retrospective/ePortfolio Tuesday 13 Oct 11:55 PM.

Source

• Week 11 Integrity Testing — Monash Panopto