How I Stopped Manually Clicking Verification Emails in My Selenium Tests

There is a specific kind of frustration that comes from having a nearly-complete automated test suite — one that handles login, forms, payments, navigation — and then hitting a wall at email verification. You can automate the browser flawlessly. But the moment your app sends a "verify your email" message, someone has to actually read it. In most teams, that someone is still a human, which means your CI pipeline either skips the step, mocks it away, or breaks at 2 AM when a developer accidentally uses the shared test inbox. I spent way too long doing it wrong before finding a setup that actually works. Here is everything I learned. Why the Common Approaches All Break Eventually I have tried most of the workarounds that come up when you search for this problem: Shared Gmail account — works until it doesn't. Two parallel test jobs submit signups at the same time and each reads the other's OTP. Flaky tests that are impossible to debug. Hardcoded temp mail URL — you need a second Selenium s