E2E Testing Patterns
v1.0.0Build reliable, fast E2E test suites with Playwright and Cypress. Critical user journey coverage, flaky test elimination, CI/CD integration.
⭐ 5· 5.9k·57 current·59 all-time
by@wpank
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (E2E patterns for Playwright and Cypress) match the SKILL.md content and code examples. Minor traceability concern: the skill metadata lists no homepage/source and README references a GitHub tree and various local-copy install commands — lack of a clear upstream repository reduces auditability but does not contradict the claimed purpose.
Instruction Scope
SKILL.md stays on-topic: it contains configuration examples, patterns, fixtures, and debugging advice for E2E tests. Example code references placeholders like createTestUser/deleteTestUser and uses process.env.CI in config — these are expected examples, not instructions to read unrelated files or exfiltrate data. Users must implement or review helper functions (e.g., createTestUser) before running them.
Install Mechanism
No install spec and no shipped code means the skill is instruction-only (lowest install risk). README shows recommended local copy commands and an npx/Clawhub install hint; there is no automated download of arbitrary archives or remote executables in the skill itself.
Credentials
The skill declares no required environment variables or credentials. Example snippets reference common CI env vars (process.env.CI) which are appropriate and proportional for CI-aware test config.
Persistence & Privilege
always is false and the skill is user-invocable; there is no indication the skill will try to persist itself or modify other skills or system configs. Being instruction-only, it does not request elevated presence.
Assessment
This is a documentation-style skill providing E2E testing patterns — it does not ask for secrets or install code itself. Before using: (1) verify the origin/source (no homepage is listed) and prefer copying examples from a known repository if available; (2) review and implement helper functions (createTestUser, deleteTestUser, network mocks) so they don't talk to production systems or leak data; (3) inspect any CI/installation commands you run (the README references an npx add GitHub path and local copy steps) to ensure they fetch from a trusted repo; and (4) treat example configs (baseURL, credentials used in examples) as templates — replace with safe test endpoints and test accounts.Like a lobster shell, security has layers — review code before you run it.
latestvk97789bbce457x1421s1pge11n80wk39
License
MIT-0
Free to use, modify, and redistribute. No attribution required.