QA test checklist

Reproducible end-to-end scenarios covering onboarding unlocks, waivers, privacy guards, meetings, and reports exports. Progress and notes save locally per tester.

Overall

0/48 steps (0%)

Onboarding module unlock logic

Required tasks control module progression; optional tasks never block; waivers count as complete; new required tasks auto-assign only to eligible in-progress agents.

Required tasks block the next module

pending

Role: AgentSuggested: Rookie agent0/3

Why: A single incomplete required task must keep the next module locked.

Step 1Open /onboarding and expand the current module.
Expect: One or more tasks show a 'Required' badge; next module has a padlock.
Step 2Complete every task EXCEPT one required task.
Expect: Module progress bar < 100%. Next module still locked. Hovering the padlock explains why.
Step 3Complete the last required task.
Expect: Module reads 100%. Next module unlocks in the sidebar and timeline; 'Continue onboarding' hero targets it.

Tester notes

Optional tasks never block progression

pending

Role: AgentSuggested: Rookie agent0/2

Why: Optional items are recommended but must not gate downstream modules.

Step 1In an in-progress module, leave every optional task unchecked but complete all required tasks.
Expect: Module still marks complete; next module unlocks.
Step 2Return later and complete an optional task.
Expect: Task check flips without altering module status; audit entry recorded.

Tester notes

Waiving a required task unblocks progression

pending

Role: Super AdminSuggested: Karla or Dylan0/3

Why: Only Super Admins can waive, and a waived task must count toward completion.

Step 1Open an agent detail page and choose 'Waive' on a required task.
Expect: Modal REQUIRES a reason (< 3 chars is rejected server-side).
Step 2Provide a reason and confirm.
Expect: Task status = 'skipped'; module progress advances; audit_log has task.waived with the reason.
Step 3As the agent, reload /onboarding.
Expect: Waived task shown greyed with the reason; next module unlocks if it was the last blocker.

Regression signatures to flag as blockers:

Waiving without a reason succeeds (trigger enforce_waiver_reason missing).

Tester notes

Reopening a completed task re-locks correctly

pending

Role: Super Admin0/2

Why: Reopening must recompute module completion and re-lock later modules if it was required.

Step 1Reopen a required task in a completed module.
Expect: Module drops below 100%; downstream unlocked modules that hadn't been started re-lock.
Step 2Reopen an optional task.
Expect: Module remains complete; downstream modules unchanged.

Tester notes

New required task auto-assigns to eligible agents

pending

Role: Super Admin0/2

Why: assign_template_to_eligible_agents trigger must only touch agents currently in that module.

Step 1In /admin/workflow add a NEW required task template to a module.
Expect: Active agents currently in-progress on that module receive the task instance; agents who already finished the module do NOT.
Step 2Add an OPTIONAL task template.
Expect: No back-fill assignment triggered.

Tester notes

Graduation ignores triggered modules

pending

Role: Super Admin0/2

Why: First Buyer / First Listing triggered modules should not block graduation.

Step 1Take an agent who has finished every base module but has open First Buyer tasks.
Expect: 'Graduate' action is enabled.
Step 2Graduate them.
Expect: Status flips to graduated; base modules become read-only; triggered modules remain writable.

Tester notes