nubente (mλumλu)

Another email mistake that I see often is running e2e test suites against your production instance, and using made up generated email addresses to sign up test users. When you do this, you generate huge numbers of bounces (emails sent to non-existent email addresses), which is not good for your sender reputation, and can result in emails sent to your real users landing in spam. It also clogs up your logs and users tables with a bunch of junk data. If you are running e2e tests that involve signing up users, use a real email address (normally via a mail tester service), or if your auth code/provider supports it, use a "test email" address which allows account creation without email delivery. If you're using @clerk, you can use a test email and/or phone (clerk.com/docs/guides/develo…) for this and it won't send anything, and you can use "424242" as the OTP every time, which makes your tests run a lot faster too.