playwright-e2e

스타3

포크1

업데이트2026년 7월 23일 22:15

Playwright specs, fixtures, traces, browsers, test projects, gated suites, or e2e Docker cleanup. Not for unit-test-only changes.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

ilude

ilude/dotfiles

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Playwright E2E Workflow

Boundary

Use playwright-e2e for browser end-to-end behavior and suite triage. Use typescript for unit-level TypeScript implementation. Use docker when only container files are changing.

Triage Rules

For requested multi-spec or suite triage:

Work one spec file at a time so progress is resumable.
Record each in-scope file as pass, fail, or skip with the reason and exact command.
Respect dependency gates. Do not run suites that require unavailable services, credentials, seeded data, or prior jobs unless those dependencies are ready.
Preserve traces, screenshots, videos, or logs needed to explain failures.
Run repository-owned teardown after triage. Do not remove volumes unless the workflow requires it.

Practical Steps

Identify the Playwright config, affected project, browser target, base URL, and required services.
Run the smallest affected spec first.
Fix or document the root cause before moving to another spec.
Run a broader suite only when shared impact, repository policy, or the requested triage scope requires it.

Quick Commands

Purpose	Commands
One file	`<package-manager> playwright test path/to/spec.ts`
One project	`<package-manager> playwright test --project=<project>`
Trace viewer	`<package-manager> playwright show-trace <trace.zip>`
Report	`<package-manager> playwright show-report`
Docker cleanup	`docker compose down --remove-orphans`

Anti-patterns

Jumping between many failing files without recording status.
Calling a suite green when dependency-gated tests were skipped without reasons.
Leaving test infrastructure running when the requested workflow owns teardown.
Treating screenshots alone as proof without checking the assertion, trace, or browser console context.

이 저장소의 다른 Skills

같은 저장소

pi-extension

ilude/dotfiles

Pi extensions and tool policy: extensions/*.ts, hooks, registerTool, promptGuidelines, registerCommand, footer/status UI, tool_result, session hooks, or subprocesses. Not for slash-command placement; use pi-command.

2026-08-023

docs

ilude/dotfiles

README, CHANGELOG, docs/, RFCs, ADRs, guides, or Markdown structure. Not for prose cleanup or archival work.

2026-07-273

no-ai-slop

ilude/dotfiles

Prose cleanup for filler, hype, vague claims, repetition, detection tells, or uncited specifics. Not for Markdown architecture or archival work.

2026-07-273

planning

ilude/dotfiles

Requirements, user stories, acceptance/verification criteria, or testable outcomes. Not for PRD drafting (/prd) or Pi /goal prompts.

2026-07-273

prd

ilude/dotfiles

Use for /prd-it or to draft, refine, or review a Product Requirements Document. Not for acceptance criteria, planning, or Pi /goal prompts.

2026-07-273

pi-log-analytics

ilude/dotfiles

Pi session, trace, metrics, routing, workflow-friction, workflow-telemetry, usage, or local JSONL analysis with DuckDB. Use for aggregating or correlating Pi runtime logs. Not for adding telemetry, generic SQL/database design, or non-Pi logs.

2026-07-273

name	playwright-e2e
description	Playwright specs, fixtures, traces, browsers, test projects, gated suites, or e2e Docker cleanup. Not for unit-test-only changes.

Playwright E2E Workflow

Boundary

Use playwright-e2e for browser end-to-end behavior and suite triage. Use typescript for unit-level TypeScript implementation. Use docker when only container files are changing.

Triage Rules

For requested multi-spec or suite triage:

Work one spec file at a time so progress is resumable.
Record each in-scope file as pass, fail, or skip with the reason and exact command.
Respect dependency gates. Do not run suites that require unavailable services, credentials, seeded data, or prior jobs unless those dependencies are ready.
Preserve traces, screenshots, videos, or logs needed to explain failures.
Run repository-owned teardown after triage. Do not remove volumes unless the workflow requires it.

Practical Steps

Identify the Playwright config, affected project, browser target, base URL, and required services.
Run the smallest affected spec first.
Fix or document the root cause before moving to another spec.
Run a broader suite only when shared impact, repository policy, or the requested triage scope requires it.

Quick Commands

Purpose	Commands
One file	`<package-manager> playwright test path/to/spec.ts`
One project	`<package-manager> playwright test --project=<project>`
Trace viewer	`<package-manager> playwright show-trace <trace.zip>`
Report	`<package-manager> playwright show-report`
Docker cleanup	`docker compose down --remove-orphans`

Anti-patterns

Jumping between many failing files without recording status.
Calling a suite green when dependency-gated tests were skipped without reasons.
Leaving test infrastructure running when the requested workflow owns teardown.
Treating screenshots alone as proof without checking the assertion, trace, or browser console context.