Test Tools
Internal use only — seed / reset test data on the live site
Admin Login
Resets [email protected] to a fresh pending inbox. Run this before each full end-to-end test.
Seed any email address as a subscriber with a fresh pending inbox — no Stripe checkout required. Once seeded, all portal actions below will use this email.
[email protected]Full provision → portal → support → teardown cycle
- 1.Seed Subscriber — Resets inbox to pending — always start here
- 2.Clear Portal Data — Wipes sessions, OTPs, and tickets for a clean slate
- 3.Bypass OTP Login — Injects a session token — then open /portal
- 4.Run Provision Wizard — Complete the wizard at /portal → should reach forwarding_active (or use Set Provisioned shortcut below to skip)
- 5.Verify Portal Dashboard — Confirm inbox status, subscriber info, and wizard completion state display correctly
- 6.Seed Test Ticket — Creates a sample ticket so the Support tab has data
- 7.Verify Support Tab — Open /portal → Support tab — confirm ticket renders with correct status and priority
- 8.Update ticket via /admin — Change status and add staff notes — confirm customer-side visibility on reload
- 9.Trigger Teardown — Moves inbox to pending_teardown; optionally suppress email
- 10.Finalise — Marks inbox deprovisioned — verify portal reflects deprovisioned state
- 11.Seed Subscriber again — Reset for the next run
Skips the wizard — resets the test inbox directly to forwarding_active so you can test teardown without re-running setup.
Moves the test inbox to pending_teardown and optionally sends the notification email to [email protected].
Marks the test inbox as deprovisioned. Inbox must be in pending_teardown first.
Deletes all portal sessions, OTP tokens, and support tickets for [email protected]. Run this first for a clean test.
Creates a valid 2-hour portal session for [email protected] and injects the token into sessionStorage. Then open /portal — it will land directly on the dashboard, skipping OTP.
Creates a sample Open / MEDIUM support ticket for the test subscriber. Use this to verify the portal Support tab renders tickets correctly.
Creates OG-test1 and OG-test2 admin accounts (idempotent — safe to run multiple times).
Reads document.documentElement.dataset.ogExtension — the attribute the extension writes at document_start.