DevOps Email Tests Need a Handoff Contract

说明与用途

在 CI 流水线中，电子邮件测试经常因临时邮箱的隐式所有权而失败。引入基于 JSON 清单的交接合同，明确定义所有者、状态和元数据，确保可靠的验证、清理和证据保留。

问题

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.

来源