DevOps Email Tests Need a Handoff Contract

Описание и применение

В CI‑пайплайнах тесты электронной почты часто падают из‑за неявного владения временными почтовыми ящиками. Введение контракта передачи, основанного на JSON‑манIFEST, позволяет явно определить владельца, статус и метаданные, обеспечивая надёжную проверку, очистку и сохранение доказательств.

Задача

Email tests in CI often fail when a disposable inbox is created in one job and read in another, especially under parallel builds.

Результат

Explicit handoff contracts reduce flaky email test failures, clarify ownership, and preserve evidence for debugging.

Рабочий процесс

• Create disposable inbox and record opaque fixture ID
• Write fixture ID and metadata to a run-scoped artifact
• In test job, claim the fixture by verifying run ID and shard
• Consume the expected email message and record its ID
• Finalize by saving manifest, decision log, and accepted message ID, then close the fixture

Доказательства

Email tests in CI often fail at the boundary between two jobs: one job creates a disposable inbox, another job tries to read it, and nobody can say who owns the inbox in between.

Источник

The setup step creates a fixture, records its identity, and gives the next step enough evidence to consume it safely.

Источник

Keep the lifecycle small enough to explain in one minute: Created, Handed off, Claimed, Consumed, Closed.

Источник