Skills e2e-testing
๐Ÿ“ฆ

e2e-testing

Content revision r1 Safe โš™๏ธ External commands

Build Reliable Playwright E2E Workflows

End-to-end coverage becomes inconsistent when setup, browser checks, visual tests, and CI integration are planned separately. This skill organizes them into one Playwright workflow.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 78 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" from https://skillstore.io/skills/sickn33-e2e-testing.md and its manifest at https://skillstore.io/api/skills/sickn33-e2e-testing/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.

Test it

Using "e2e-testing". Plan end-to-end coverage for a customer sign-in and checkout flow.

Expected outcome:

  • Setup: configure Chromium, Firefox, and WebKit with reusable authenticated fixtures.
  • Scenarios: verify sign-in, cart updates, payment validation, order confirmation, and error recovery.
  • Evidence: retain traces and screenshots for failures, then enforce the suite in continuous integration.

Using "e2e-testing". Add visual regression checks for a responsive product page.

Expected outcome:

  • Capture approved baselines for desktop and mobile viewports.
  • Mask dynamic content and define a reviewed difference threshold.
  • Run comparisons across supported browsers and publish failed images as CI artifacts.

Security Audit

Safe
v5 โ€ข 7/23/2026 Open versioned report

All 30 static findings are false positives caused by Markdown inline-code markers and fenced-code delimiters. SKILL.md contains a documented testing workflow and plain prompts, with no executable shell or Ruby statements and no prompt injection evidence.

1
Files scanned
171
Lines analyzed
0
Review items
0
False positives ignored
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/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/security.svg)](https://skillstore.io/skills/sickn33-e2e-testing?utm_source=security_passport_badge)

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-e2e-testing.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 security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-e2e-testing/audits/5

BibTeX citation

@techreport{sickn33-sickn33-e2e-testing-2026, author = {sickn33}, title = {e2e-testing security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-e2e-testing/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 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/audits/5" identifiers: - type: other value: "skillstore:sickn33-e2e-testing:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

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

What You Can Build

Launch E2E Coverage

Plan Playwright setup, directory structure, browser configuration, and initial test flows for a web application.

Standardize Release Testing

Define critical journeys, visual checks, browser coverage, and quality gates for repeatable release validation.

Integrate Browser Tests

Plan parallel execution, artifacts, reports, and notifications for Playwright tests in continuous integration.

Try These Prompts

Set Up Playwright
Plan a Playwright setup for [application], including test directories, browsers, shared configuration, and one critical user journey.
Design Critical Flows
Create an end-to-end test strategy for [application], covering critical flows, test data, page objects, fixtures, and assertions.
Plan Visual And Browser Coverage
Design visual regression and cross-browser coverage for [pages], including baselines, thresholds, Chromium, Firefox, WebKit, and mobile emulation.
Build A CI Quality Gate
Plan CI execution for [repository], including parallel jobs, retries, traces, screenshots, videos, reports, artifacts, and failure notifications.

Best Practices

  • Prioritize critical user journeys before expanding browser and visual coverage.
  • Use stable fixtures and explicit assertions to keep tests independent and repeatable.
  • Retain traces, screenshots, and reports so CI failures can be diagnosed.

Avoid

  • Do not automate every interface path before defining release-critical flows.
  • Do not accept visual baseline changes without reviewing the rendered differences.
  • Do not rely on fixed delays when observable page states can determine readiness.

Frequently Asked Questions

Does this skill install Playwright?
No. It plans installation and configuration steps, while the selected agent or companion skill performs implementation.
Can it create Playwright tests?
It guides test design and implementation prompts. Detailed test generation depends on project context and referenced companion skills.
Which browsers are covered?
The workflow includes Chromium, Firefox, WebKit, and mobile browser emulation.
Does it support visual regression testing?
Yes. It covers baseline images, visual assertions, comparison thresholds, and difference reviews.
Can it integrate tests with CI/CD?
Yes. It plans parallel execution, artifacts, reporting, notifications, and quality gates for continuous integration.
What project information is required?
Provide the application scope, critical journeys, environments, authentication method, test data, supported browsers, and release criteria.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Ref

88a8e9a07f4c54ab105c1c41b6267c287146b07b

Maintenance freshness

7/26/2026

Usage

18 downloads ยท 132 views

File structure

๐Ÿ“„ SKILL.md

More from sickn33

View all
View all