Playwright Email Tests: Diagnose the Real Failure

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

Тесты Playwright для проверки email часто завершаются неинформативным сообщением «verification email not found». В статье предлагается собирать метаданные на каждом этапе, использовать ограниченное ожидание и классифицировать ошибки по четырём категориям, чтобы быстро выявлять причину сбоя.

Задача

Email verification tests often fail with vague “verification email not found” messages, masking the true cause across multiple system boundaries.

Результат

Tests become diagnostic tools: failures are classified, evidence is attached, and retries are informed by concrete data, reducing flakiness and debugging time.

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

• 1. Submit signup form and capture response metadata (status, elapsed time, mailbox).
• 2. Attach signup metadata to test artifacts.
• 3. Poll inbox with bounded timeout, filtering by recipient, subject, and run token.
• 4. On timeout, throw error with last observed subject.
• 5. After test, review attached metadata to determine failure category (submission, queue, delivery, read).
• 6. Use failure taxonomy to decide whether to retry or investigate further.

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

Playwright can attach a compact diagnostic record when a step fails.

Источник

Use bounded polling instead of fixed sleeps to avoid unnecessary delays.

Источник