Despite mature end-to-end testing setups like Playwright or Cypress with CI/CD integration, testing email workflows remains a significant challenge for engineering teams. Critical user flows such as email verification, OTP authentication, password resets, magic links, and team invitations often lack robust automated testing. Teams commonly resort to custom solutions to address this gap. These solutions include using shared inboxes, polling email provider APIs like Gmail or Outlook, or running internal mail servers like MailHog/Mailpit. Some teams even opt to mock email delivery entirely or simply bypass testing these crucial email-dependent parts of the user journey. This oversight is concerning, as the inability for users to verify accounts or reset passwords effectively renders the application unusable. The author is seeking insights into how other teams manage these email workflows within their end-to-end tests. They specifically inquire if actual email flows are tested end-to-end and whether dedicated email testing tools or internal solutions are employed. The author also asks about the primary difficulties encountered and, for Playwright users, how OTP and magic-link workflows are handled. The goal is to understand the diverse approaches to solving this recurring testing problem.