Fictional audit users and realistic QA commands are available on the public domain.

Journey categories

Preconditions

• Guest preview is enabled for at least one lesson or module card.
• A guest session can store a lightweight wishlist or recently viewed item.

Expected outcome

• Public content stays public and gated content stays gated.
• The signup flow explains whether guest state will migrate or reset.
• After account creation, the saved module context is preserved or clearly disclosed as non-portable.

Negative or edge variant

Guest cookies are blocked or expired, so the user is told exactly what will not carry over instead of silently losing state.

Journey categories

Preconditions

• Email signup is enabled in the test environment.
• Verification emails are captured in a test mailbox or sink.

Expected outcome

• The account is created in an unverified state with clear next-step guidance.
• The first valid verification link succeeds and activates the account.
• A resend flow exists and does not create duplicate accounts.

Negative or edge variant

The user taps an expired or already-used link and gets a safe resend path instead of a generic failure page.

Journey categories

Preconditions

• The account is active and has at least one prior device or session on record.
• MFA enrollment is available in the test environment if the product supports it.

Expected outcome

• The login flow succeeds only after the required step-up checks complete.
• The new-device event is visible in account security history or notification copy.
• MFA setup is confirmed without locking the user out of the current session.

Negative or edge variant

Repeated bad codes or passwords trigger rate-limited messaging without leaking whether the account exists.

Journey categories

Preconditions

• Password reset is enabled and sends a one-time or short-lived link.
• Support-assisted recovery exists or is intentionally unavailable with clear policy text.

Expected outcome

• The expired link is rejected cleanly.
• A new reset can be requested without creating multiple conflicting recovery states.
• If mailbox access is unavailable, the product routes the user to the documented recovery channel.

Negative or edge variant

The user clicks a stale reset link from another device and the system must fail closed without confusing cross-session behavior.

Journey categories

Preconditions

• The environment exposes either self-serve billing or a partner-scoped price simulation.
• At least one valid and one invalid discount or scholarship code are configured.

Expected outcome

• Price, discount, entitlement scope, and any refund or billing note are visible before confirmation.
• The enrollment result matches the selected plan or scholarship state.
• A receipt, invoice, or enrollment confirmation is generated if applicable.

Negative or edge variant

An expired or invalid code does not apply silently and does not alter the final entitlement unexpectedly.

Journey categories

Preconditions

• The account is in a renewal-failed or grace-period state.
• The billing UI or support handoff exposes the next required action.

Expected outcome

• The user sees the renewal status, due amount, and access window clearly.
• Updating the payment method or invoice route restores access without erasing progress.
• Support or policy links explain what happens if payment is not recovered.

Negative or edge variant

A second payment failure must not double-charge the user or silently strip access without an explanation.

Journey categories

Preconditions

• At least one lesson includes video plus a downloadable source asset.
• The media player or asset list exposes quality or retry behavior where supported.

Expected outcome

• Playback degrades gracefully or offers a fallback instead of freezing.
• Downloadable assets are labeled clearly for offline reading.
• The user can resume the lesson later without losing place unnecessarily.

Negative or edge variant

A stalled network request surfaces a retry state or fallback asset instead of leaving the user on a dead loading spinner.

Journey categories

Preconditions

• A quiz flow exists with keyboard-reachable controls.
• The environment supports screen reader and high-contrast checks.

Expected outcome

• Focus order is predictable and all quiz controls are labeled.
• Timer messaging, submission status, and validation errors are announced clearly.
• Autosave or recovery behavior preserves answers if the page refreshes.

Negative or edge variant

Any focus trap, missing label, or inaccessible validation message is logged as a blocker instead of treated as cosmetic.

Journey categories

Preconditions

• A course or module completion threshold is configured.
• Certificate issuance or completion badge logic is available in the test environment.

Expected outcome

• Completion status matches the recorded progress.
• The certificate or badge uses the correct learner identity and completion date.
• Any follow-up notifications match the actual completion event.

Negative or edge variant

A recalculated quiz score or late sync must not revoke a certificate silently or produce a mismatched completion record.

Journey categories

Preconditions

• The product distinguishes marketing from transactional or learning-critical notifications.
• Cookie or analytics preferences are exposed if the product supports them.

Expected outcome

• Granular preference settings persist after refresh and re-login.
• Critical transactional notices remain appropriately scoped.
• Preference screens explain what cannot be turned off and why.

Negative or edge variant

Unsubscribing from marketing must not disable password-reset, billing, or security notifications unintentionally.

Journey categories

Preconditions

• Authenticated privacy-rights actions are available or routed to support.
• The account has enough history to validate export completeness.

Expected outcome

• The export includes the documented data categories for the user only.
• Deletion explains what is removed immediately and what is retained by policy.
• Active sessions are revoked after deletion is confirmed.

Negative or edge variant

The export omits a major data class or the deletion flow fails without telling the user what happened next.

Journey categories

Preconditions

• The account is locked or flagged after a suspicious event.
• Session-management or forced re-authentication controls are available.

Expected outcome

• The warning explains what triggered the lock or review state at a high level.
• Current and prior sessions can be reviewed or revoked safely.
• The account returns to a known-good state after recovery.

Negative or edge variant

Stale sessions survive the recovery flow or the user cannot tell whether the account is safe again.

Journey categories

Preconditions

• Creator enrollment or role elevation is enabled in the test environment.
• Content policy acceptance is required before publish rights are granted.

Expected outcome

• The creator role is inactive until required steps are completed.
• Policy acceptance is timestamped and visible in the creator record.
• The UI distinguishes draft rights from publish rights clearly.

Negative or edge variant

A partially configured creator should not be able to publish or expose incomplete public metadata.

Journey categories

Preconditions

• Draft authoring is enabled.
• The course model supports required metadata and validation.

Expected outcome

• Draft save works without data loss.
• Missing required metadata is called out before publish.
• The preview reflects the latest saved version.

Negative or edge variant

A required field such as prerequisites or entitlement scope must not fail silently during save or publish.

Journey categories

Preconditions

• Large media or document upload is enabled.
• At least one large file is available in the test environment.

Expected outcome

• The upload flow resumes or retries without creating duplicate assets.
• The creator can tell which version is current.
• Partial or failed uploads do not become publicly visible.

Negative or edge variant

A dropped connection leaves an orphaned asset, duplicate attachment, or inconsistent file-type state.

Journey categories

Preconditions

• The course includes at least one video, one document, and one image or card-style visual.
• Accessibility metadata fields are exposed in authoring.

Expected outcome

• Accessibility fields are clearly attached to the relevant asset.
• Publish warnings appear if required metadata is missing.
• Learner views render the metadata correctly.

Negative or edge variant

A creator can publish inaccessible media with no warning or cannot tell which assets still lack accessibility metadata.

Journey categories

Preconditions

• Scheduled publishing is enabled.
• Course and account timezone settings are configurable.

Expected outcome

• The schedule reflects an explicit timezone and release time.
• Notifications or status indicators confirm when the release occurred.
• Learner-facing availability matches the configured schedule.

Negative or edge variant

Daylight-saving or timezone mismatches cause content to publish early or late with no visible warning.

Journey categories

Preconditions

• A published lesson already has active learners and recorded progress.
• Versioning or republish behavior is available.

Expected outcome

• Learner progress is preserved or changes are explained explicitly.
• Existing lesson links continue to resolve where intended.
• A version or change log is recorded for auditability.

Negative or edge variant

Republishing unexpectedly restarts lessons, invalidates quiz attempts, or changes public slugs without redirection.

Journey categories

Preconditions

• Quiz authoring supports attempts, due dates, and accommodation overrides.
• At least one learner profile can receive an accommodation rule in the test environment.

Expected outcome

• The quiz rules are visible and saved correctly.
• The accommodation applies only to the intended learner or cohort.
• Learner-facing timing, messaging, and submission states stay consistent.

Negative or edge variant

Accommodation settings leak to unintended learners or are ignored for the targeted learner at runtime.

Journey categories

Preconditions

• An integrity or policy flag exists on a learner submission or creator asset.
• The relevant content policy is visible to the reviewer.

Expected outcome

• Evidence, policy basis, and next actions are visible in one workflow.
• The decision is logged and reversible through a documented appeal path.
• Affected users receive a clear explanation without exposing internal-only notes.

Negative or edge variant

A false positive leaves the creator or learner with no context, no appeal path, or no retained evidence.

Journey categories

Preconditions

• A published asset is under complaint or review.
• The creator has access to a takedown workflow or moderation handoff.

Expected outcome

• The takedown action is logged with reason and timestamp.
• Learners see an appropriate replacement or explanation if access changes.
• Appeal or review status is visible to the creator.

Negative or edge variant

The lesson disappears abruptly with no trace, no communication, or no way to distinguish temporary hold from permanent removal.

Journey categories

Preconditions

• Creator analytics or digests are enabled.
• At least one course has learner activity to summarize.

Expected outcome

• Analytics are aggregate or scoped appropriately.
• Notification cadence is configurable.
• Exports or digests do not expose raw personal data that the creator does not need.

Negative or edge variant

The analytics view exposes support-only fields, sensitive user notes, or other data outside creator scope.

Journey categories

Preconditions

• Reviewer or collaborator roles are supported in the test environment.
• The creator owns more than one draft or published course.

Expected outcome

• The collaborator receives only the intended scope.
• Role boundaries are visible in the invitation or permissions UI.
• All permission grants are logged.

Negative or edge variant

A collaborator gains access to unrelated courses, learner billing details, or creator-wide settings.

Journey categories

Preconditions

• Support tooling exposes identity-safe duplicate-email diagnostics.
• The user can verify ownership through an approved recovery path.

Expected outcome

• The agent can distinguish existing account, alias conflict, and merge-review cases safely.
• The user receives a precise next step without exposing another person's account state.
• Any account merge or cleanup action is logged.

Negative or edge variant

The agent can accidentally merge the wrong records or disclose whether another user's account exists beyond policy.

Journey categories

Preconditions

• The support console exposes lock reason and verification checklist.
• The account is actually in a locked or risk-review state.

Expected outcome

• The support agent can verify identity without bypassing policy.
• Unlock actions revoke stale sessions if required.
• The account owner receives a clear recovery notice.

Negative or edge variant

The account is unlocked without sufficient proof, or old sessions stay valid after the incident is resolved.

Journey categories

Preconditions

• Support billing view is available with redacted payment details.
• The user has an invoice or renewal history in the system.

Expected outcome

• The agent can see billing status, redacted payment metadata, and invoice history only.
• The invoice can be reissued or downloaded safely.
• Billing notes are consistent with user-facing entitlement state.

Negative or edge variant

The support view exposes sensitive payment secrets or the invoice history does not match the actual entitlement record.

Journey categories

Preconditions

• A transaction, scholarship record, or manual billing case exists.
• Refund and adjustment policies are documented.

Expected outcome

• The decision path and monetary effect are logged.
• The user sees whether access changes immediately, later, or not at all.
• Support can cite the applicable policy or pilot rule.

Negative or edge variant

The refund is duplicated, the credit is applied to the wrong learner, or access is removed with no explanation.

Journey categories

Preconditions

• The platform supports linked guardian-minor records.
• The learner account remains pending until consent is confirmed.

Expected outcome

• Guardian relationship and consent scope are logged with timestamps.
• Minor access activates only after successful approval.
• Support can explain revocation and community restrictions clearly.

Negative or edge variant

Minor access opens before approval is finalized, or the consent record lacks enough detail to audit later.

Journey categories

Preconditions

• An authenticated rights request or verified support workflow is available.
• The user has enough history to validate export completeness.

Expected outcome

• The export includes the documented user data categories and timestamps.
• The request lifecycle is logged end to end.
• The export excludes data belonging to other users or staff-only notes that should remain internal by policy.

Negative or edge variant

A major data class is missing, or unrelated user data leaks into the export package.

Journey categories

Preconditions

• Deletion is either self-serve or support-assisted with identity verification.
• Retention exceptions are documented.

Expected outcome

• Sessions are revoked and the account enters the documented deletion state.
• The user receives clear messaging about any retained billing, security, or abuse records.
• The deletion action is audit logged.

Negative or edge variant

The user still has active access after deletion, or the support workflow cannot explain retained records.

Journey categories

Preconditions

• A moderation queue or abuse-report workflow exists.
• Trust-and-safety staff can see the report context and policy rules.

Expected outcome

• The moderation decision is logged with reason and timestamp.
• The affected user receives a notice consistent with policy.
• The appeal or review state is visible internally.

Negative or edge variant

The action is overbroad, irreversible, or lacks an audit trail explaining why it happened.

Journey categories

Preconditions

• A status surface or banner exists for public communication.
• Support staff can reference incident notes or canned responses.

Expected outcome

• The public status update is scoped, timestamped, and consistent with support guidance.
• The issue can be marked resolved or updated without leaving stale copy behind.
• Users know whether the workaround is retry, fallback download, or wait.

Negative or edge variant

The status page, banner, and support responses drift apart or stay stale after the incident is fixed.

Journey categories

Preconditions

• The product surfaces rate-limit or browser-support errors in a user-visible way.
• Support has guidance for retry windows and supported environments.

Expected outcome

• Messages explain the problem in plain language and avoid blame.
• Retry timing, supported browsers, and fallback options are explicit.
• Help content is readable and keyboard accessible.

Negative or edge variant

The user only sees a generic failure page with no retry window, no browser guidance, and no accessible error summary.

Journey categories

Preconditions

• A public security disclosure contact or intake route exists.
• Trust-and-safety or engineering routing ownership is documented.

Expected outcome

• The report receives an acknowledgement within the documented response target.
• Internal escalation and ownership are recorded.
• Public responses avoid requesting risky public reproduction steps.

Negative or edge variant

The report is lost, handled by the wrong queue, or answered with instructions that would weaken security posture.

Journey categories

Preconditions

• Enterprise or pilot commercial routing exists in the test environment.
• The workspace can be created with a defined seat count.

Expected outcome

• Seat count, billing owner, term, and support expectations are explicit.
• The quote or trial state can be reviewed before activation.
• The manager receives a named next step for procurement or pilot support.

Negative or edge variant

Seat limits, pricing assumptions, or support scope remain ambiguous after the commercial setup flow finishes.

Journey categories

Preconditions

• SSO or domain restriction is enabled in the test environment.
• A test identity provider is available if SSO is supported.

Expected outcome

• Configuration values are validated before go-live.
• A rollback or safe-test path exists before enforcing the policy for all seats.
• Auth rules are visible enough for a manager to understand the impact.

Negative or edge variant

A bad SSO configuration or domain rule locks out valid users without a safe recovery path.

Journey categories

Preconditions

• An enterprise workspace already exists.
• Invite and seat-state tracking are enabled.

Expected outcome

• Invite state is visible and refreshable.
• Assigned content matches the intended learning path.
• Reminder messaging is configurable and tied to real invitation status.

Negative or edge variant

Expired or duplicate invites consume seats incorrectly or show the wrong activation state.

Journey categories

Preconditions

• A seat is currently assigned to a departing user.
• Transfer or reclaim rules are defined for the workspace.

Expected outcome

• The seat can be reclaimed or reassigned cleanly.
• Historical completion and access records remain attributable for reporting.
• The departing user's access ends on the correct date.

Negative or edge variant

The seat is stuck, the history becomes orphaned, or the former user retains access after offboarding.

Journey categories

Preconditions

• Enterprise billing records exist in the test environment.
• The workspace has at least one completed billing cycle.

Expected outcome

• Invoices and seat reports align with the visible contract details.
• Files are downloadable and labeled by billing period.
• The manager can tell what is estimate versus final invoice data.

Negative or edge variant

Seat counts, dates, or currencies differ between the dashboard and the downloadable invoice.

Journey categories

Preconditions

• A manager dashboard exists with scoped reporting.
• The workspace has at least a few invited or active learners.

Expected outcome

• The manager view is aggregate or role-appropriate by default.
• Sensitive learner data stays out of managerial reporting.
• Access boundaries are consistent across UI, exports, and notifications.

Negative or edge variant

The manager can see private notes, raw support correspondence, or billing identifiers that are outside their role.

Journey categories

Preconditions

• Partner-ready documentation exists or is routed through support.
• The manager can request materials without opening a generic learner ticket.

Expected outcome

• The right documents or support route are surfaced clearly.
• The manager sees who owns follow-up and expected response timing.
• Policy references match the current product behavior.

Negative or edge variant

The request falls into a generic queue with no owner, stale documentation, or no response expectation.

Journey categories

Preconditions

• Role-based or category-based notification preferences are available.
• More than one stakeholder email can be configured for the workspace if supported.

Expected outcome

• Notification categories are clearly separated by purpose.
• Urgent incident messages bypass the digest cadence when appropriate.
• Billing notices route only to the intended owner or finance contact.

Negative or edge variant

Notifications are all-or-nothing, or high-volume digests drown out critical incident notices.

Journey categories

Preconditions

• A linked guardian-minor workflow exists.
• The minor account remains pending until consent is resolved.

Expected outcome

• Consent scope, community restrictions, and notification choices are explicit.
• The guardian can tell exactly what was approved.
• Revocation or change steps are documented.

Negative or edge variant

The guardian cannot distinguish consent for learning access from consent for marketing, community participation, or analytics.

Journey categories

Preconditions

• The guardian account is linked to exactly one learner in the test setup.
• Progress and privacy-rights views are available for guardians if policy allows them.

Expected outcome

• The guardian sees only the linked learner's data.
• Correction or export requests are logged against the correct learner record.
• The UI distinguishes guardian rights from the learner's own account rights.

Negative or edge variant

The guardian can see data from unrelated learners or cannot tell whether a request applies to the guardian or the child record.

Journey categories

Preconditions

• The workspace contains user, progress, and billing history.
• Org offboarding or workspace closure is supported in the test environment.

Expected outcome

• Export completes before destructive steps begin.
• The manager sees what will be retained by policy after closure.
• Access removal is timestamped and auditable.

Negative or edge variant

The workspace deletion begins before export completion or no retention disclosure is shown during offboarding.