playwright-e2e-screenshots

Automate Playwright end-to-end tests with per-test screenshots for visual verification.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ahostbr/dotcodex --skill playwright-e2e-screenshots
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-e2e-screenshots
Source: https://github.com/ahostbr/dotcodex/tree/main/skills/playwright-e2e-screenshots
Command: npx skills add https://github.com/ahostbr/dotcodex --skill playwright-e2e-screenshots

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end browser testing with visual verification to quickly catch UI regressions and reduce manual QA effort.

Core Features & Use Cases

  • Create E2E Playwright tests with screenshots, one assertion per test.
  • Capture and review verification images at each phase to validate UI behavior.
  • Organize screenshots under e2e/screenshots/ and reuse across tests.

Quick Start

Create E2E Playwright tests with screenshots and review each phase before moving to the next test.

Frequently Asked Questions about playwright-e2e-screenshots

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

FAQPage Schema
How do I automate visual verification in Playwright E2E tests?

Automate visual verification in Playwright E2E tests by capturing per-test screenshots and reviewing the images to validate UI behavior before proceeding to the next test. This reduces manual QA effort when catching UI regressions.

How do I organize Playwright screenshots for cross-browser testing?

Organize Playwright screenshots for cross-browser testing by saving verification images under the e2e/screenshots/ directory. This structure allows you to systematically store and reuse captured images across multiple E2E tests.

Do I need Chromium configured to run Playwright E2E visual verification?

Yes, you need Playwright configured with Chromium to run E2E visual verification. The browser automation environment must be properly set up to capture screenshots and perform cross-browser UI regression validation.

What is the best way to catch UI regressions in browser automation tests?

The best way to catch UI regressions in browser automation tests is to use E2E Playwright tests with visual verification, creating one screenshot assertion per test to isolate failures and validate exact UI behavior at each phase.

Can I reuse screenshots across multiple Playwright E2E tests?

Yes, you can reuse screenshots across multiple Playwright E2E tests by organizing verification images under e2e/screenshots/. This allows different tests to reference the same captured UI baseline for regression validation.