Playwright Test Instructions

复制 Prompt

/goal
GOAL:
Complete Playwright Test Instructions for a project with failing or missing verification gates: Create path-specific Playwright instructions that enforce stable locators, isolated tests, explicit assertions, cross-browser coverage, and CI behavior.

CONTEXT:
- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.
- Inspect test suites, lint config, CI logs, coverage reports, and failing output.
- Establish a baseline by running or locating evidence for: `.github/instructions/playwright-tests.instructions.md with glob front matter, sample e2e test, and passing Playwright command`.

CONSTRAINTS:
- Keep the scope limited to this goal; do not expand into unrelated cleanup.
- Do not weaken tests, delete assertions, or mask errors to make verification pass.
- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.
- Do not weaken lint, typecheck, or test rules to create a green result.
- Fix production or fixture causes before changing expectations.

DONE WHEN:
- The implementation or documentation directly satisfies: Create path-specific Playwright instructions that enforce stable locators, isolated tests, explicit assertions, cross-browser coverage, and CI behavior.
- The verification command or evidence path succeeds: `.github/instructions/playwright-tests.instructions.md with glob front matter, sample e2e test, and passing Playwright command`.
- The final diff is scoped to the relevant files and has no unrelated formatting churn.

VERIFY:
- Run `.github/instructions/playwright-tests.instructions.md with glob front matter, sample e2e test, and passing Playwright command` or the closest repo-local equivalent if the exact command is not available.
- Capture before/after evidence for the behavior, metric, report, or artifact involved.
- If verification cannot run locally, stop and report the missing dependency instead of guessing success.

OUTPUT:
- Summarize changed files, key decisions, verification output, and remaining risks.
- Include any follow-up that is required for production rollout or human review.

STOP RULES:
- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.
- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.
- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.