GitHub Actions Email Tests Need Evidence

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

Тесты отправки писем в CI теперь генерируют набор доказательств, позволяющий быстро диагностировать причины неудач, вместо случайных повторов.

Задача

Email verification tests in CI often fail with vague messages, making it hard to diagnose whether the issue is timing, inbox sharing, or API rejection.

Результат

Email tests now produce consistent evidence bundles that turn flaky failures into quick investigations, reducing retry cycles and improving test reliability.

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

• Generate a unique correlation ID for each test run
• Run email tests with continue-on-error=true
• Upload evidence artifacts using actions/upload-artifact@v4 with if: always()
• If tests failed, exit with failure after artifacts are uploaded

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

The key is to write these files even when a retry succeeds. Otherwise, the first failure disappears and the green result hides a slow or broken dependency.

Источник

Upload artifacts with if: always() is the important line.

Источник