Skip to main content
ttr qa users gives agents real, signed-in accounts in a deployed environment (for example a Meet rehearsal with one staff host and 40 participants) without touching real users. Every account is disposable: it carries an immutable test marker, a reserved address, a run expiry, and is deleted automatically.

Accounts

The database (private.qa_test_users and the guard_qa_test_auth trigger) refuses any qa_* marker change, any address change, any signup that claims a reserved address, and any attempt to add the marker to an existing account. Deletion re-checks the marker and the reserved address before anything is removed, so the QA path cannot delete a real account. The migration refuses to apply while any existing account already uses a reserved address or marker. QA accounts never verify as staff, including --staff hosts on the staff domain: isVerifiedTuturuuuStaffSession and private.staff_identity_verified return false for any marked account, so staff-only surfaces (support inbox, short links, staff workspace secrets, domain entitlements, Mira and mail tools) stay closed. Meet hosting is the one explicit exception: canVerifiedAccountHostMeeting admits a --staff QA host until its run expires. Give hosts --tier pro so meetings get paid-tier capacity. A QA account can never join the root workspace, hold a platform role or allowance, change its Auth role, or operate this API.

Test tiers

--tier plus|pro grants the tier through the normal entitlement row (public.workspace_subscriptions, status active) on the account’s personal workspace and on the run workspace. The row’s provider ID uses the reserved qa_test_ prefix and is registered in private.qa_test_subscriptions; no billing provider object exists, so checkout, invoices, seat billing and revenue reporting never include it. Billing tools that reconcile with the provider skip qa_test_ rows. Deleting the account cancels its test subscriptions.

Run workspace

--workspace creates one shared workspace for the run, named [QA] <purpose> <run>. The first activated account owns it, so create the host first, then append participants with --run. Every account in the run joins it. It is deleted with the run’s last account. Personal workspaces cannot be deleted; they keep the same retained state as an ordinary account deletion.

Operators

The API under /api/v1/admin/qa/test-users admits verified staff sessions that hold manage_qa_test_users in the root workspace. Root administrators hold it implicitly; grant it to a dedicated QA-operator role for anyone else. The CLI uses the ttr login session.

Commands

Passwords, cookies and tokens are never printed or returned in --json output. Passwords go to the macOS Keychain (service tuturuuu-qa, account = address) or, elsewhere or with --password-store file, to ~/.tuturuuu/qa/<run>/credentials.json. Sessions go to ~/.tuturuuu/qa/<run>/<userId>.storage-state.json (or .tokens.json). Directories are 0700, files 0600, and symlinked targets are refused. TUTURUUU_QA_HOME overrides the root for tests. Delete and cleanup remove the local files and Keychain items of deleted accounts.

Sessions

session mints a fresh session without the password: the server generates a magic-link token (no email is sent), verifies it, and returns the Supabase session cookies for the requested origin. The origin must share the deployment’s session cookie scope (for example any https://*.tuturuuu.com app when called on tuturuuu.com); this sets cookie attributes only, because the session tokens work from any client. The request must be JSON. Every mint is audited. A session lives until the run expires, when cleanup bans the account (so refresh stops even if the delete has to be retried) and then deletes it; delete the account earlier to revoke sooner.

Expiry cleanup

Cron Control job qa-test-user-cleanup runs every 15 minutes as a native Cloudflare Worker processor (apps/cron-control/src/processors/qa-test-user-cleanup.ts). It calls the ledger RPCs and the Auth admin API with the service key; no web route is involved. Each slot lists at most 25 expired accounts and deletes them one at a time within a 90-second deadline. The ledger leases each deletion for 10 minutes. The Worker removes the run workspace with its last account and records that before the account settles, bans then deletes the Auth account, and settles only after Auth reports it absent. The cleanup fence is checked when each deletion begins and the Cron Control fence before every destructive request. A refused step leaves the lease to lapse and fails the slot; an unconfirmed write ends the slot as unknown before another deletion starts. A later slot re-verifies either; nothing is replayed blindly. Repeated failures trip Cron Control’s consecutive-failure stop. The Worker does not run Meet attendance subject erasure. Attendance rows of these synthetic accounts age out through attendance retention. ttr qa users cleanup uses the web operator path, which erases them immediately; run it when a QA pass ends. The job is off until qa-test-user-cleanup is listed in CRON_CONTROL_ENABLED_JOBS. Until then, run ttr qa users cleanup --expired after each run: Auth does not expire the accounts by itself.

Audit

private.qa_test_user_events records create, session, delete, workspace_create and workspace_delete with the actor (operator with user ID, or cron), run and account. It holds IDs, tier, purpose and timestamps only.

Regression coverage

  • apps/database/supabase/tests/qa-test-users.sql: reserved addresses, marker immutability, the Auth insert-then-update ordering, staff exclusion, root and platform-role confinement, tier grants, leased deletion, stop fence.
  • Auth admin ordering is verified once against the local Auth server: reserve, auth/v1/admin/users create, activate, magic-link verify, ban (refresh refused), workspace and account delete, settle.
  • apps/web/src/lib/qa-test-users/*.test.ts and the route tests under apps/web/src/app/api/v1/admin/qa/test-users/.
  • apps/cron-control/src/processors/qa-test-user-cleanup.test.ts: fences, request order, leased unknown outcomes, key headers. The processor was also run once against the local Supabase and Auth stack.
  • packages/sdk/src/cli/qa-users.test.ts: secret handling and file modes.