JFK Training V2 — UAT Testing Walkthrough

Grounded in current Salesforce UAT guidance (SFDC Developers, TestMonitor, Apex Hours):

• Freeze the sandbox. No metadata deploys into JFKBox during the test window, so every tester sees the same state.
• Mirror real permissions. Admin steps run as a System Administrator; guest steps run as the unauthenticated Guest User (hence incognito). Don't "test as admin" the guest portal.
• Test the whole story, not features. Each scenario below is an end-to-end flow (register → confirm → complete → badge), not an isolated field check.
• One action, one observable result per step. Every step has an … line. Mark Pass/Fail against it — avoid vague "it works".
• Include negative scenarios. Section 6 covers empty fields and invalid date order. Don't only test the happy path.
• Log results centrally. Record Pass/Fail/Blocked + screenshots in the results table (or your tracker). Triage defects daily.
• Written sign-off. The business owner signs off in writing at the end — not "looks good".

Scenario G1 — Happy-path registration (both parts)

1. In the incognito window, open the portal link.
   The registration component loads with no login prompt and no error banner.
2. Step 1 — Stakeholder & Category. Open the Stakeholder dropdown and choose UAT Stakeholder - JFK Training (V2).
   The Stakeholder appears in the list.
3. Open the Category dropdown and choose Placeholder Category 1.
   Only classes for that stakeholder + category appear; UAT Class - Familiarization (V2 Test) is listed.
4. Select the class and continue.
   Advances to session selection.
5. Step 2 — Sessions. Pick the Part 1 session, then the Part 2 session.
   Both upcoming sessions show date/time in Eastern Time with seats remaining; Part 2's date is after Part 1's.
6. Step 3 — Attendee details. Enter First name, Last name, a real Email you can access, phone, and complete any PPE / consent inputs shown.
   Required fields validate; you cannot continue with blanks.
7. Step 4 — Review & submit. Confirm the summary, then click Submit / Register.
   A success confirmation is shown on screen.
8. Check the inbox for the email you entered.
   A confirmation email arrives, From the org-wide address, times shown in Eastern Time, with a QR code and a link back to the site. No badge "tier" wording.

Verify the guest registration landed (switch to admin)

1. In your normal (logged-in) browser, open the UAT Class → Related → sessions, or query Enrollments.
   A new Contact was created for the attendee, with one Confirmed enrollment on Part 1 and one on Part 2.
2. Confirm the seats-remaining count on each session dropped by 1 versus the capacity of 20.

Scenario A1 — Completion sets badge + completion flag

1. Open Enrollment — Part 1 and set Status = Completed; Save.
2. Open Enrollment — Part 2 and set Status = Completed; Save.
3. Open UAT Tester One.
   Badged__c = true and Training Completed = true on the Contact. The completion is tier-independent (no Badge Level required).
4. If a completion email is configured, the attendee receives a "training complete" email with no tier wording.

Scenario A2 — Cancellation notification

1. On either enrollment, set Status = Cancelled; Save.
   A cancellation email (JFK Cancellation Email) is sent to the attendee with the session details and site link. Only one email — no duplicate.

Scenario A3 — No-Show batch Optional

1. Set a Part 1 enrollment to a non-completed status and run the batch from Developer Console → Debug → Open Execute Anonymous:

   Database.executeBatch(new NoShowProcessor_Batch(), 200);

   Downstream Part 2 enrollment is cancelled by the batch, and the batch's own notification fires without a duplicate from the generic cancellation handler (it is suppressed during the batch).

Record one row per scenario. Attach screenshots for any Fail/Blocked. Triage defects daily; deploy fixes in batches so testers don't lose progress.