Overview

Implement a GitHub Actions workflow pipeline that runs Playwright E2E tests against a remote E2E server and automatically reports results to Microsoft Teams, GitHub, and Jira.

Current State Analysis

The following CI infrastructure already exists:

Gaps Identified

1. No Teams notification — E2E results are only reported as GitHub Issues; no Teams webhook integration exists
2. e2e-healer limited scope — Only runs login.spec.ts; full test suite + healing phase are commented out
3. No Jira integration — Failures don't create/update Jira issues for tracking
4. No PR-triggered E2E — Tests only run on schedule/manual dispatch, not on PR events
5. No structured result parsing — Watchdog relies on Copilot agent to analyze results, not structured JSON/JUnit parsing

Architecture

The project uses GitHub Agentic Workflows (gh-aw) with Copilot engine. Workflow definitions are written as Markdown (.md) files and compiled to .lock.yml via gh aw compile.

Key Files

• .github/workflows/e2e-watchdog.md — Nightly E2E watchdog definition
• .github/workflows/e2e-healer.md — E2E healer definition
• playwright.config.ts — Playwright configuration
• e2e/ — All E2E test specs (POM pattern)
• e2e/envs/.env.playwright — Environment configuration

Acceptance Criteria

• E2E test results are posted to a Microsoft Teams channel via webhook
• Notification includes: pass/fail counts, failed test names, link to HTML report artifact
• Teams notification works for both scheduled runs and manual dispatch
• e2e-healer runs the full test suite (not just login.spec.ts)
• On failure, a Jira issue is created/updated with failure details
• Documentation for required GitHub Secrets is updated

JIRA Issue: FR-2559