androidengineers.Book a session

Customer evaluation and UAT

Lab: run a structured acceptance session

exerciseSelf-paced

Assignment

Prepare twelve synthetic cases across two roles: normal, ambiguous, missing-data, access-denied, timeout, and incorrect-draft scenarios.

Build sequence

  1. Write expected outcomes and severity before the session.
  2. Ask a peer to complete tasks while recording observations and friction.
  3. Log defects with reproduction steps, evidence, owner, and disposition.
  4. Write an acceptance decision tied to the exact tested version.

Acceptance checks

  • Blocking permission or workflow defects are not averaged away.
  • The report includes rejected cases and unresolved limitations.
  • Another reviewer can reproduce each reported defect from its evidence.

Evidence to keep

Submit the working artifact or decision document described above, the inputs used, and the observed results for every acceptance check. Include one failed attempt and the change you made after investigating it. Label fixture-based outcomes separately from live-system measurements. These artifacts become part of your final portfolio review.

YOUR LEARNING JOURNEY

0 of 119 available lessons completed

Progress saved in this browser. No account needed.
Lab: run a structured acceptance session | Forward Deployed Engineer | Android Engineers