Tutorial Notifications and Reports

Tutorial: Notifications and Reports

HTML/PDF reports plus Slack, Teams, email, and GitHub PR comments.

Deep: Tutorial 08.

Reports

Every pipeline ends with report → notify.

Artifact	Contents
reports/qa-summary.html	Summary, per-test table, links to screenshots/video/trace
reports/qa-summary.pdf	Same via Chromium (ENABLE_PDF_REPORT, default on)
reports/summary.json	Stable CI contract — External CI/CD
npm run report	Playwright interactive HTML report
reports/artifacts/<test>/	Failure media copies

LLM plain-English summary: ENABLE_LLM_REPORT=true. Failure RCA in report: ENABLE_LLM_ANALYSIS=true.

GitHub PR comments

Automatic when repo + PR are known (--pr-number or webhook PR event). See GitHub Integration.

Slack

SLACK_WEBHOOK_URL=https://hooks.slack.com/services/…

Block message: PASSED/FAILED, counts, summary, truncated analysis on fail.

Microsoft Teams

TEAMS_WEBHOOK_URL=https://outlook.office.com/webhook/…

MessageCard (green/red) with the same stats.

Email (+ PDF)

SMTP_HOST=smtp.example.com
SMTP_PORT=587
SMTP_USER=qa-bot@example.com
SMTP_PASSWORD=…
NOTIFY_EMAIL_TO=team@example.com

Multipart mail; PDF attached when present. Empty user/password → local unauthenticated relay.

Behavior

• Channels are independent — set only what you need
• Delivery errors don’t fail the pipeline or block other channels
• All configured channels fire on every run (pass or fail); filter in CI if you want failure-only noise

Next

Agent CI and Kubernetes · Mission Control · Configuration