스킬 playwright-best-practices

📦

playwright-best-practices

Name: playwright-best-practices
Author: currents-dev

v1.2 콘텐츠 리비전 r1 중간 위험 ⚙️ 외부 명령어🌐 네트워크 접근📁 파일 시스템 접근⚡ 스크립트 포함🔑 환경 변수

Build Reliable Playwright Tests

Fragile tests and inconsistent setup make browser testing difficult to maintain. This skill provides practical Playwright patterns for test design, debugging, and CI workflows.

지원: Claude Codex Code(CC)

⚠️ 50 나쁨

Maintain this Skill? Claim it ⚠️ 50 나쁨

설치 전에 중지하고 확인을 요청하세요.

계획을 검토하고 파일을 변경하기 전에 사용자의 명시적 동의를 받으세요.

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.

에이전트 요청

Review the Skillstore skill "playwright-best-practices" from https://skillstore.io/skills/currents-dev-playwright-best-practices.md and its manifest at https://skillstore.io/api/skills/currents-dev-playwright-best-practices/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.

에이전트가 읽기 쉬운 리소스

AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

Markdown 상세 GET /skills/currents-dev-playwright-best-practices.md 서명된 manifest GET /api/skills/currents-dev-playwright-best-practices/manifest 서명된 lockfile GET /api/skills/currents-dev-playwright-best-practices/lockfile

테스트해 보기

"playwright-best-practices" 사용 중입니다. A checkout test sometimes fails after clicking Submit.

예상 결과:

Diagnosis: the assertion runs before the checkout response updates the page.
Recommended change: register the response wait before clicking, then assert the confirmation heading.
Verification: repeat the test and inspect traces for any remaining ordering failures.

"playwright-best-practices" 사용 중입니다. Plan a faster Playwright workflow for our CI pipeline.

예상 결과:

Execution plan: divide tests across shards and isolate data by worker.
Dependency plan: align browser binaries with the installed Playwright version and cache them using the dependency lockfile.
Reporting plan: retain failure traces and merge shard reports into one result.
Safety check: verify disposable database targets before reset or restore operations.

보안 감사

중간 위험

v1 • 2026. 10. 29. 버전별 보고서 열기

Most presented alerts are benign Playwright examples; no evidence found of keylogging, prompt injection, or malicious exfiltration in reviewed context. Confirmed risks involve unguarded database operations, predictable temporary files, and indiscriminate process termination; HAR commit guidance adds a data-disclosure concern. All 400 presented findings were adjudicated; 888 omitted matches still require manual review before automatic publication. Static review was capped at 400/1288 representative findings; omitted static matches are unconfirmed, so automatic publishing stays disabled until manual review.

스캔된 파일

26,413

분석된 줄 수

검토 항목

오탐 무시됨

확인된 보안 우려 사항 (1)

중간

architecture/when-to-mock.md:160-169 architecture/when-to-mock.md:187-192

HAR Commit Guidance Omits Secret Redaction

The guide says 'Commit `.har` files to version control' after recording staging admin API traffic. Without redaction, recordings can disclose authorization headers, cookies, or sensitive response bodies through repository history.

The recording and commit recommendation are explicit, but no captured HAR was supplied. This confirms unsafe guidance, not an observed credential leak.

기능 검토 항목 (7)

이 스킬에 대해 예상될 수 있는 실제 로컬 기능이므로 검토가 필요하지만, 확인된 악의적 동작으로는 집계되지 않습니다.

높음

core/global-setup.md:163

Database connection strings

execSync(`psql $DATABASE_URL < ${SNAPSHOT_PATH}`, { stdio: "inherit" });

core/global-setup.md:163: The snapshot restore executes SQL against DATABASE_URL without verifying a disposable test database. A misconfigured connection can modify a non-test database.

높음

core/configuration.md:266

Synchronous process execution

execSync('npx prisma db push --force-reset', { stdio: 'inherit' });

core/configuration.md:266: Teardown invokes Prisma with --force-reset without validating the database target. An inherited production connection could cause irreversible data loss.

높음

core/global-setup.md:163

Synchronous process execution

execSync(`psql $DATABASE_URL < ${SNAPSHOT_PATH}`, { stdio: "inherit" });

core/global-setup.md:163: The snapshot restore executes SQL against DATABASE_URL without verifying a disposable test database. A misconfigured connection can modify a non-test database.

중간

debugging/flaky-tests.md:306

Node.js fs operations

fs.writeFileSync(file, "{}");

debugging/flaky-tests.md:306: The timestamp-based shared /tmp path is opened with writeFileSync without exclusive creation. Another local user could precreate a symlink and cause file truncation.

중간

debugging/flaky-tests.md:306

Synchronous file operations

fs.writeFileSync(file, "{}");

debugging/flaky-tests.md:306: The timestamp-based shared /tmp path is opened with writeFileSync without exclusive creation. Another local user could precreate a symlink and cause file truncation.

중간

debugging/flaky-tests.md:305

Temp directory access

const file = `/tmp/test-${Date.now()}.json`;

debugging/flaky-tests.md:305: The timestamp-based shared /tmp path is opened with writeFileSync without exclusive creation. Another local user could precreate a symlink and cause file truncation.

중간

infrastructure-ci-cd/github-actions.md:519

xargs command (can execute arbitrary commands)

run: lsof -ti:3000 | xargs kill -9 2>/dev/null || true

infrastructure-ci-cd/github-actions.md:519: The command force-kills every process returned for port 3000 without checking ownership by this test run. Shared runners could lose unrelated services.

위험 요인

⚙️ 외부 명령어 (50)

🌐 네트워크 접근 (50)

📁 파일 시스템 접근 (50)

⚡ 스크립트 포함 (4)

advanced/authentication.md:467 architecture/pom-vs-fixtures.md:141 core/configuration.md:254 core/configuration.md:265

🔑 환경 변수 (50)

advanced/authentication.md:108 advanced/authentication.md:109 advanced/authentication.md:201 advanced/authentication.md:206 advanced/authentication.md:211 advanced/authentication.md:443 advanced/authentication.md:491 advanced/authentication.md:492 advanced/authentication.md:627 advanced/authentication.md:628 advanced/authentication.md:108 advanced/authentication.md:109 advanced/authentication.md:201 advanced/authentication.md:206 advanced/authentication.md:211 advanced/authentication.md:443 advanced/authentication.md:491 advanced/authentication.md:492 advanced/authentication.md:627 advanced/authentication.md:628 advanced/third-party.md:331 advanced/third-party.md:344 advanced/third-party.md:331 advanced/third-party.md:344 advanced/third-party.md:331 advanced/third-party.md:344 architecture/when-to-mock.md:204 architecture/when-to-mock.md:219 architecture/when-to-mock.md:234 architecture/when-to-mock.md:246 architecture/when-to-mock.md:204 architecture/when-to-mock.md:219 architecture/when-to-mock.md:234 architecture/when-to-mock.md:246 core/annotations.md:39 core/annotations.md:53 core/annotations.md:88 core/annotations.md:356 core/annotations.md:366 core/annotations.md:39 core/annotations.md:53 core/annotations.md:88 core/annotations.md:356 core/annotations.md:366 core/configuration.md:44 core/configuration.md:83 core/configuration.md:84 core/configuration.md:85 core/configuration.md:87 core/configuration.md:95

감사자: codex

이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기

보고서 링크 복사

https://skillstore.io/skills/currents-dev-playwright-best-practices/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 배지

[![Skillstore security assessment](https://skillstore.io/badges/skills/currents-dev-playwright-best-practices/security.svg)](https://skillstore.io/skills/currents-dev-playwright-best-practices?utm_source=security_passport_badge)

HTML 배지

<a href="https://skillstore.io/skills/currents-dev-playwright-best-practices?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/currents-dev-playwright-best-practices/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

임베드 카드

<iframe src="https://skillstore.io/embed/skills/currents-dev-playwright-best-practices.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

학술 인용 (APA · BibTeX · CFF)

APA 인용

currents-dev. (2026). playwright-best-practices security audit report (audit version 1) [Author version 1.2]. Skillstore. https://skillstore.io/skills/currents-dev-playwright-best-practices/audits/1

BibTeX 인용

@techreport{currents-dev-currents-dev-playwright-best-practices-2026,
  author = {currents-dev},
  title = {playwright-best-practices security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/currents-dev-playwright-best-practices/audits/1},
  note = {Author version 1.2}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "playwright-best-practices security audit report (audit version 1)"
version: "1.2"
type: report
authors:
  - name: "currents-dev"
date-released: "2026-10-29"
url: "https://skillstore.io/skills/currents-dev-playwright-best-practices/audits/1"
identifiers:
  - type: other
    value: "skillstore:currents-dev-playwright-best-practices:audit:1"
    description: "Skillstore immutable audit report identifier"

변형 비교

설치 가능한 변형 3개

각 작성자의 스킬은 별도의 설치 항목으로 유지됩니다. 추천 변형은 Skillstore 근거로 순위가 정해집니다.

이 변형이 1위인 이유

Skillstore 점수가 가장 높음

작성자 / 소스 Skillstore 점수 증거 신뢰도 Skillstore 사용량 업데이트됨

0xBigBoss 권장

0xbigboss-playwright-best-practices

Skillstore 점수 79

증거 신뢰도 높음

Skillstore 사용량 90

업데이트됨

2026-10-11

currents-dev 현재

currents-dev-playwright-best-practices

Skillstore 점수 50

증거 신뢰도 중간

Skillstore 사용량 알 수 없음

업데이트됨

2026-10-29

vitalics

vitalics-playwright-best-practices

Skillstore 점수 38

증거 신뢰도 중간

Skillstore 사용량 20

업데이트됨

2026-09-09

Skillstore 점수

이 점수의 이유 증거 신뢰도: 중간

아키텍처

유지보수성

콘텐츠

커뮤니티

사양 준수

만들 수 있는 것

Add Maintainable Browser Tests

Create application tests with accessible locators, reusable setup, and assertions tied to visible behavior.

Investigate Intermittent Failures

Review flaky tests for timing errors, shared state, unstable selectors, and missing network synchronization.

Improve CI Test Workflows

Plan browser installation, caching, sharding, reports, and controlled environment setup for automated test runs.

이 프롬프트를 사용해 보세요

Write a First Browser Test

Write a Playwright test for the login flow in this project. Use accessible locators and auto-waiting assertions. Identify missing application details before assuming selectors.

Fix a Flaky Test

Review this failing Playwright test and its error output. Identify timing, locator, and isolation problems. Propose focused fixes and repeated-run verification without hiding failures.

Design Authentication Fixtures

Design Playwright fixtures for admin and member workflows in this project. Isolate worker data and protect saved authentication state. Explain which external services need mocks.

Review a Sharded CI Pipeline

Review this Playwright CI configuration for sharding, caching, reports, and database lifecycle. Restrict destructive operations to disposable test resources. Require approval before destructive changes.

모범 사례

Use accessible locators and auto-waiting assertions that describe observable application behavior.
Isolate test data and authentication state; keep credentials and sanitized recordings out of unintended publication paths.
Review destructive setup commands before execution and verify changes with targeted, repeated test runs.

피하기

Replacing reliable synchronization with fixed sleeps or excessive retries.
Sharing mutable users, sessions, or database state across parallel workers without isolation.
Running database resets against unverified targets or committing recordings without secret redaction.

자주 묻는 질문

Does this skill install Playwright or run browsers automatically?

No. It provides guidance and examples. Browser execution requires an available tool environment, installed dependencies, and project configuration.

Can I use it with Claude, Codex, and Claude Code?

The skill declares support for all three tools. Available file access and command execution depend on your configured environment.

Which test types does it cover?

It covers end-to-end, API, component, visual, accessibility, security, and performance testing, with additional Electron and browser extension examples.

Can it help with flaky tests?

Yes. It documents trace analysis, locator improvements, synchronization, test isolation, and repeated runs. Application-specific evidence is still required.

Should every service be mocked?

No. The guidance favors real application integrations and controlled mocks for external services. Select boundaries according to the behavior under test.

Are database cleanup examples safe to copy unchanged?

No. Validate disposable test targets and require approval for destructive operations. Protect credentials, saved sessions, and recorded traffic before sharing artifacts.