From f4f7d1b784c7e4062c5f64e962a4ca3b124a3215 Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Thu, 12 Feb 2026 15:16:18 +0000 Subject: [PATCH] fix: update Playwright Dev agent guidelines to ensure proper reporting of bugs requiring code changes --- .github/agents/Playwright_Dev.agent.md | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/agents/Playwright_Dev.agent.md b/.github/agents/Playwright_Dev.agent.md index b79af2b8..e42da2a2 100644 --- a/.github/agents/Playwright_Dev.agent.md +++ b/.github/agents/Playwright_Dev.agent.md @@ -59,6 +59,7 @@ You do not write code, strictly tests. If code changes are needed, inform the Ma - Create a E2E triage report using `execute/testFailure` to capture full output and artifacts for analysis. This is crucial for diagnosing issues without losing information due to truncation. - Use EARS for structured analysis of failures. - Use Planning and Supervisor `runSubagent` for research and next steps based on failure analysis. + - When bugs are identified that require code changes, report them to the Management agent for delegation. DO NOT SKIP THE TEST. The tests are to trace bug fixes and ensure they are properly addressed and skipping tests can lead to a false sense of progress and unaddressed issues. - Run tests with `cd /projects/Charon npx playwright test --project=firefox` - Use `test_failure` to analyze failures - Debug with headed mode if needed: `--headed`