test-e2e

스타11

포크0

업데이트2026년 4월 16일 05:32

Generates end-to-end tests for a user flow using Playwright or Cypress

설치

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

출처

berkcangumusisik

berkcangumusisik/claude-code-practices

다운로드

Flow to test: $ARGUMENTS

cat package.json | grep -E "playwright|cypress|puppeteer"
ls e2e/ tests/ cypress/ playwright/ 2>/dev/null | head -20

Read 2-3 existing E2E test files to understand the project's patterns, selectors, and helpers.
Generate the E2E test covering:
- Setup (auth if needed, navigation to starting point)
- The full user flow step by step
- Assertions at each key step
- Teardown / cleanup
Use data-testid selectors by preference, then aria labels, then text - avoid CSS class selectors.
Place the test in the correct directory matching project conventions.
Note any test data or environment variables required.

이 저장소의 다른 Skills

같은 저장소

Analyzes the current session's token usage, pinpoints where tokens were wasted, and produces concrete optimization actions

Generates API documentation from route definitions (Express, Fastify, Hono, etc.)

Adds caching to expensive operations - Redis, in-memory, HTTP cache headers

Staged değişiklikleri analiz edip Conventional Commits formatında commit mesajı oluşturur

Reports cyclomatic complexity hotspots and refactoring suggestions

Finds unused functions, variables, exports, and dependencies across the codebase

name	test-e2e
description	Generates end-to-end tests for a user flow using Playwright or Cypress
argument-hint	<flow-description>
user-invocable	true
allowed-tools	Read Glob Edit Bash
effort	medium

Flow to test: $ARGUMENTS

cat package.json | grep -E "playwright|cypress|puppeteer"
ls e2e/ tests/ cypress/ playwright/ 2>/dev/null | head -20

Read 2-3 existing E2E test files to understand the project's patterns, selectors, and helpers.
Generate the E2E test covering:
- Setup (auth if needed, navigation to starting point)
- The full user flow step by step
- Assertions at each key step
- Teardown / cleanup
Use data-testid selectors by preference, then aria labels, then text - avoid CSS class selectors.
Place the test in the correct directory matching project conventions.
Note any test data or environment variables required.