playwright-e2e

Detect visual regressions in Svelte UI changes with Playwright screenshots.

Updated Nov 4, 2025
One-click install
npx skills add https://github.com/TrevorS/strieber-gpt-3 --skill playwright-e2e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-e2e
Source: https://github.com/TrevorS/strieber-gpt-3/tree/main/.claude/skills/playwright-e2e
Command: npx skills add https://github.com/TrevorS/strieber-gpt-3 --skill playwright-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Visual E2E testing ensures Strieber chat UI renders correctly after changes to Svelte components, CSS, or layout, catching regressions before release and reducing manual QA time.

Core Features & Use Cases

  • End-to-end UI regression tests: Validate rendering of key components after frontend changes.
  • Visual regression with screenshots: Capture desktop and mobile views to detect layout shifts.
  • Efficient onboarding for changes: Integrates with existing docker-compose setup to run tests in CI or locally.

Quick Start

Run the tests with the Playwright runner: docker compose run --rm playwright-test

After tests complete, view screenshots in frontend/test-results/screenshots/ for desktop and mobile: frontend/test-results/screenshots/layout-desktop.png frontend/test-results/screenshots/layout-mobile.png You can verify results with:

  • Use the Read tool to inspect the produced PNGs

Frequently Asked Questions about playwright-e2e

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect visual regressions in my frontend UI after making changes?

Visual regression testing captures screenshots of your UI before and after changes, comparing them to detect unintended layout shifts, styling issues, or rendering problems. This Skill uses Playwright to automate screenshot capture across desktop and mobile viewports, catching regressions that manual testing might miss.

Can I run E2E visual tests for Svelte components and CSS changes?

Yes. This Skill validates rendering of Svelte components, CSS modifications, and layout structure changes by executing headless Playwright tests and comparing visual output. It enforces a production build step and captures screenshots to verify layout, theme, and responsiveness across devices.

What's the quickest way to set up visual E2E testing in my CI/CD pipeline?

Run tests using the integrated docker-compose setup: `docker compose run --rm playwright-test`. Tests execute headless, generate organized screenshots in frontend/test-results/screenshots/, and produce desktop and mobile views for verification—no additional configuration needed if your environment already uses docker-compose.

Do I need to manually review every screenshot after running E2E tests?

Screenshots are automatically captured to frontend/test-results/screenshots/ organized by viewport (desktop, mobile). You review the PNG outputs to confirm UI renders correctly; the Skill structures test locations and enforces organized output so regression detection is systematic rather than ad-hoc.

How does visual testing reduce manual QA effort for frontend changes?

Visual E2E testing automates the verification step by capturing and comparing UI state across predefined scenarios and viewports. Instead of manually testing each layout variant, you run automated Playwright tests that detect layout shifts and styling regressions instantly, freeing QA to focus on edge cases and user workflows.