Skills e2e-testing-patterns
📦

e2e-testing-patterns

Content revision r2 Safe ⚙️ External commands🌐 Network access🔑 Env variables

Build Reliable End-to-End Test Suites

End-to-end tests often become slow, flaky, and difficult to maintain. This skill provides Playwright and Cypress patterns for stable workflows, test data, CI, debugging, and accessibility.

Supports: Claude Codex Code(CC)
🥉 79 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "e2e-testing-patterns" from https://skillstore.io/skills/sickn33-e2e-testing-patterns.md and its manifest at https://skillstore.io/api/skills/sickn33-e2e-testing-patterns/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-e2e-testing-patterns.md Signed manifest GET /api/skills/sickn33-e2e-testing-patterns/manifest Signed lockfile GET /api/skills/sickn33-e2e-testing-patterns/lockfile

Test it

Using "e2e-testing-patterns". Plan E2E coverage for a subscription checkout.

Expected outcome:

  • Prioritize sign-in, plan selection, payment success, declined payment, and confirmation.
  • Use isolated customer data and mock third-party payment responses outside dedicated integration checks.
  • Assert visible confirmation, account entitlement, and cleanup after each run.

Using "e2e-testing-patterns". Diagnose a Cypress test that fails while waiting for a user list.

Expected outcome:

  • Replace fixed delays with an aliased user request and wait for its successful response.
  • Assert the visible list state after the response instead of checking internal implementation details.
  • Capture screenshots and request details on failure to separate application defects from timing problems.

Using "e2e-testing-patterns". Recommend CI coverage for a cross-browser checkout suite.

Expected outcome:

  • Run focused Chromium checks on every change and broader Firefox and WebKit checks before release.
  • Shard independent tests, retain traces on retry, and store screenshots and videos only for failures.
  • Keep destructive scenarios in an isolated test environment with dedicated accounts.

Security Audit

Safe
v5 • 7/23/2026 Open versioned report

All 23 static alerts are false positives caused by Markdown, TypeScript syntax, standard test configuration, and expected local test traffic. The files contain documentation and code samples, with no executable scripts, prompt injection, credential exfiltration, or malicious intent. Environment-based administrator credentials should remain limited to isolated test accounts and protected CI secrets.

2
Files scanned
582
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (3)
resources/implementation-playbook.md:160-194 resources/implementation-playbook.md:331-337 SKILL.md:44
🌐 Network access (4)
resources/implementation-playbook.md:249 resources/implementation-playbook.md:326 resources/implementation-playbook.md:65 resources/implementation-playbook.md:289
🔑 Env variables (8)
resources/implementation-playbook.md:57 resources/implementation-playbook.md:58 resources/implementation-playbook.md:59 resources/implementation-playbook.md:174 resources/implementation-playbook.md:57 resources/implementation-playbook.md:58 resources/implementation-playbook.md:59 resources/implementation-playbook.md:174
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-e2e-testing-patterns/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-e2e-testing-patterns/security.svg)](https://skillstore.io/skills/sickn33-e2e-testing-patterns?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-e2e-testing-patterns?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-e2e-testing-patterns/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-e2e-testing-patterns.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). e2e-testing-patterns security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-e2e-testing-patterns/audits/5

BibTeX citation

@techreport{sickn33-sickn33-e2e-testing-patterns-2026, author = {sickn33}, title = {e2e-testing-patterns security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-e2e-testing-patterns/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "e2e-testing-patterns security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-e2e-testing-patterns/audits/5" identifiers: - type: other value: "skillstore:sickn33-e2e-testing-patterns:audit:5" description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score
sickn33 Recommended Current

sickn33-e2e-testing-patterns

Skillstore Score 79
Evidence Confidence High
Skillstore usage 15
Updated

2026-08-21

wshobson

wshobson-e2e-testing-patterns

Skillstore Score 77
Evidence Confidence High
Skillstore usage 18
Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
91
Spec Compliance

What You Can Build

Stabilize regression suites

Replace fixed waits and brittle selectors with deterministic conditions, isolated fixtures, and user-visible assertions.

Cover critical product journeys

Design maintainable browser tests for authentication, checkout, profile updates, responsive interfaces, and accessibility.

Scale browser tests in CI

Configure retries, browser projects, sharding, traces, screenshots, videos, and structured reports for continuous delivery.

Try These Prompts

Plan a critical journey 
Review [workflow] for [application]. Define the critical path, required test data, stable selectors, success criteria, and cleanup steps.
Design a Playwright suite 
Design a Playwright E2E suite for [feature]. Include page objects, fixtures, deterministic waits, browser coverage, failure artifacts, and accessibility checks.
Refactor flaky Cypress tests 
Analyze these Cypress test symptoms: [details]. Identify likely causes and propose stable selectors, intercepts, assertions, test isolation, and debugging steps.
Architect CI browser coverage 
Create an E2E strategy for [system] and [CI platform]. Balance sharding, retries, real integrations, mocks, visual checks, artifacts, security, and runtime.

Best Practices

  • Test user-visible behavior and reserve E2E coverage for critical journeys.
  • Use stable role, label, or data-attribute selectors with deterministic waits.
  • Create isolated test data, clean it after each test, and protect credentials in CI.

Avoid

  • Do not use fixed delays when the test can wait for a specific state or response.
  • Do not couple test order or reuse mutable data across independent scenarios.
  • Do not run destructive test flows against production systems or real customer data.

Frequently Asked Questions

Which frameworks does this skill cover?
It provides implementation patterns for Playwright and Cypress.
Can it execute or validate my tests?
No. It provides guidance and examples, but your project environment must run and validate the tests.
Does it help with flaky tests?
Yes. It covers deterministic waits, stable selectors, isolation, traces, screenshots, videos, and debug modes.
Does it support accessibility testing?
Yes. It includes Playwright examples using axe-core for page and form accessibility checks.
How should test credentials be handled?
Use dedicated test accounts and protected CI environment variables. Never expose credentials in logs, artifacts, or production tests.
Should every behavior have an E2E test?
No. Focus E2E coverage on critical journeys and use unit or integration tests for lower-level logic and edge cases.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/e2e-testing-patterns

Ref

88a8e9a07f4c54ab105c1c41b6267c287146b07b

Maintenance freshness

7/26/2026

Usage

13 downloads · 156 views

File structure

📁 resources/

📄 implementation-playbook.md

📄 SKILL.md

More from sickn33

View all

Related Skills

View all