Settings — Regression Test

Covers general and account settings. Dictation prefs are covered in dictation; calendar and notification toggles in meeting-detection; plans and billing in billing-and-paywall.

Steps

1. Open Settings → App and toggle Launch on startup on.
   • The toggle persists; the app is set to open at login
2. In App → Appearance, change Keyboard sound to Typewriter, then type somewhere.
   • The typewriter keypress sound plays; switching to Black Ink changes the sound; None silences it
3. Open Settings → Account, change Preferred name, and click Save.
   • A "Preferred name saved" confirmation appears
   • Reopening Account shows the new name
4. In Settings → Account, look at the Sign-in email section at the top.
   • It shows your sign-in email address
   • On a Google or Apple account, a small provider mark and label ("Google" or "Apple") appear next to the email
   • On an email/password account, a Change password button appears instead
5. On an email/password account, click Change password.
   • A confirmation toast reads "If an account exists for this email, we sent a password reset link."
   • The reset email arrives and its link opens Firebase's password-reset page
6. Open Settings → Help, write feedback, and click Send to the team.
   • A "Feedback sent successfully" confirmation appears

Account actions

7. Click Sign Out (bottom of the settings menu) and Cancel the confirmation.
   • A confirmation dialog appears; Cancel keeps you signed in
8. In Account → Delete account, click Delete account.
   • A confirmation dialog requires typing DELETE ACCOUNT to enable the destructive button
   • Cancel closes it with the account intact
9. On a throwaway account, actually complete the deletion.
   • It succeeds — you are signed out, not left staring at an error
   • Signing in again with the same Google account gives a brand-new empty workspace, with onboarding shown again
   • If the deletion fails, report the exact message and what still works — do not assume nothing happened. The steps run in order (payment provider, then sign-in identity, then your data), so a failure partway can leave you signed out with some data already removed. Say whether you can still sign in, and whether your documents are still there

Note: only complete the actual sign-out / account deletion on a throwaway account — both are destructive.

Known limitation, by design: an account whose plan was set through QA → Entitlements cannot be deleted. The QA plan writes a placeholder subscription id, and deletion asks Stripe to cancel it, which Stripe refuses because no such subscription exists. This is expected, not a bug to file.

Two ways round it, both click-only:

• Set the plan back to Basic in the QA panel first — that clears the placeholder, and the deletion then goes through.
• Or delete the account before you set any plan on it.

The same applies to any account whose stored subscription no longer exists in Stripe. If you hit a failed deletion on an account you never touched with the QA panel, that is worth reporting.