Playwright throwaway email

A throwaway habit fixes the address field: mint a unique local-part for each test, type it, continue. On dummyemails.org humans debugging a failing spec can land on the console, Copy an auto-minted address, and watch the inbox. For CI, treat the generator as a fixture pattern: each test gets its own string, preferably via a helper that will later call an API when you expose one.

What Playwright should not do: scrape a public temp mail site as a critical path. Public inboxes are slow, noisy, and unsafe for staging secrets. Prefer application hooks that expose the last token in test environments, route interception, or an owned-domain receive pipeline you control. The throwaway still matters because the app database uniqueness constraint is real even when mail is stubbed.

Practical fixture sketch in words: beforeEach mint address, store on test info, fill the email locator, proceed. On failure, the address in the trace is disposable, so recordings do not leak personal mail. Refresh and Change map to human recovery when you are not in headless mode.

Relate to Cypress with a different runner story, not the same paragraph. Relate to OTP testing when the assertion is the code screen. Relate to owned-domain guides when receive is part of the suite.

Dummyemails.org positioning stays QA: twenty minute homepage TTL for long debug sessions, ten minute page when you want a short fused timer, TLD chips only for domains you can receive on. No anonymity pitch. No lifting competitor docs.

Give every Playwright test its own throwaway email and your flake chart gets quieter on the signup axis.