BUR Trial Registration — End-to-End Test Console

Click a green button to open a registration page (guest), submit the form, then click a blue/grey button to confirm the record was created as an admin.

Guest registration page Admin verify (record / list) Admin — supporting link

Environment: BURBox sandbox  •  Site: /trials  •  baseline at build: 0 registrations, 0 team members
0 / 0 tests passed
Best practice: open the guest registration pages in a private/incognito window (so you are NOT logged in as an admin). This truly exercises the guest user. Keep this file open in your normal window for the admin verify links.
1

Advanced Trial 1 — internal single volunteer

Component: BUR Volunteer Trial Registration • locked to Advanced Trial 1 • cap 80 • no family

Steps

  1. Enter First name, Last name, a unique Email, phone.
  2. Pick a Department (e.g., Example Partner Organization).
  3. Leave participation type = Single Traveler.
  4. Check the 3 consents, enter waiver initials, optionally the marketing opt-in.
  5. Click Register.
✔ Green success message. A new Contact is created under the chosen Account, and a Trial Registration (Status = Confirmed) links to it.
2

Advanced Trial 2 — family / group + partner org

Component: BUR Volunteer Trial Registration • family ON • cap 310

Steps

  1. Fill the primary registrant (unique email), pick a Department.
  2. Set participation type to a Family option.
  3. Click Add party member twice; fill names (one can be an email-less minor — tick Minor).
  4. Accept consents + initials, then Register.
3 Trial Registrations created: the primary plus 2 children (children have Parent Registration set to the primary). New Contacts created under the chosen Account.

Confirm as admin

Recent Trial Registrations Open the primary → check the Parent Registration children.
3

Integrated Trial — public, family with minor

Component: BUR Volunteer Trial Registration • family ON • no cap

Steps

  1. Fill the primary registrant with a unique email.
  2. For Department, choose Public / Community (the default for public registrants).
  3. Add a party member and tick Minor.
  4. Accept consents + initials, then Register.
✔ Registrations created under the Public / Community Account. No cap error regardless of volume.
4

Contact matching — email, then name

Reuses an existing Contact instead of creating a duplicate

4a — Match by email

  1. Register once with email match.test@example.com.
  2. Register again with the same email but a different name.
✔ The 2nd registration links to the same Contact (no duplicate Contact for that email).

4b — Match by name (no email hit)

  1. Register with a first+last name that already exists but a new email.
✔ Links to the existing Contact matched by First + Last name.
5

Validation — consents & waiver required

The form must block incomplete submissions

Steps

  1. Fill name/email but leave the liability waiver unchecked (or blank initials) → click Register.
  2. Then uncheck privacy/terms and retry.
✔ A clear error appears (“Please accept the privacy policy, terms, and liability waiver…”) and no record is created.
6

Staff Participants — add a worker by email

Component: BUR Staff Trial Sign-Up • authenticated • auto “Staff” role
This page is login-required. Open it in your normal (logged-in) window as a coordinator/admin who has the BUR Trial Staff Coordinator permission set.

6a — Happy path

  1. Enter the email of an active Salesforce user (e.g., your own login email).
  2. Tick one or more trials → Add to trial(s).
✔ A Trial Team Member is created per trial, linked to that User, with Trial Role = Staff (Status Active). The "Staff" role already exists on each seeded trial (Default).

6b — Error path

  1. Enter an email that has no Salesforce user (e.g., nobody@nowhere.example.com) → submit.
✔ A clear error: “No user found for … Staff must have a Salesforce user…”. No record created.

Admin quick links

Jump straight to the seeded records and object lists

BURBox sandbox • Checklist state is saved in your browser (localStorage). Admin links require you to be logged into Salesforce in the same browser.