Run Tokens Make Email CI Less Fragile

Short summary

A practical pattern for making email-based CI tests reliable: generate a unique run token per test, embed it in the email-triggering request, and assert the token exists in the message body before consuming any links. This prevents tests from grabbing the wrong email in shared or concurrent inboxes. The author includes a concrete code example and recommends logging inbox IDs, centralizing polling logic, and validating identity before acting on email content.

• •Generate a unique run token per test and embed it in the email-triggering request payload
• •Assert the token exists in the message body before extracting links or codes — don't rely on 'latest email' or timestamps
• •Centralize email polling in one helper and log inbox ID, subject, and receive time on failure for easier debugging

Generated with AI, which can make mistakes.