Email tests become confusing when the UI, the test runner, and the delivery provider all speak different languages. A React component waits for a verification state, while a Node.js service waits for a message, and the test waits for both. When something is slow, the failure usually says only that a button never changed.
The fix I like is a small TypeScript contract between the application and its mail test adapter. It makes the boundary explicit, gives every scenario a stable identity, and lets the same React test move from a fast fake transport to a real disposable mail address when the delivery path needs coverage.
The boundary is the product of the test
An email test is not just an assertion about a message.…