Signup email is usually treated like a small feature: submit a form, send a message, then show a success state. In a real React product, it becomes a boundary between browser state, an API, a mail provider, and a test inbox. When those concerns leak into each other, the UI gets hard to reason about and the tests become slow or flaky.
I have found it more useful to treat email delivery as a replaceable product dependency. The React screen should know that a verification request was accepted. It should not know if the message went through a provider API, a local fake, or a disposable email account used by an end-to-end test.
That separation makes a signup flow easier to ship, and it gives the team a cleaner place to inspect failures.…