skills.rest
open-metadata
open-metadataOFFICIAL
Explore all skills by this author →
Website𝕏@open_metadataGitHub

playwright-validation

Validate branch UI changes with Playwright end-to-end tests.

14.8k|2.3k|Updated Aug 1, 2021
Search Tags:#browser automation#test coverage#playwright#e2e testing#ui validation#branch review
One-click install
npx skills add https://github.com/open-metadata/OpenMetadata --skill playwright-validation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwright-validation
Source: https://github.com/open-metadata/OpenMetadata/tree/main/.claude/skills/playwright-validation
Command: npx skills add https://github.com/open-metadata/OpenMetadata --skill playwright-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill validates UI changes in a branch by guiding Playwright end-to-end testing to ensure new code paths are exercised and no regressions slip through.

Core Features & Use Cases

  • Review branch changes against UI tests using Playwright MCP to identify gaps.
  • Analyze existing Playwright tests for the modified components and add missing scenarios.
  • Validate visual and interactive behavior across key UI flows and prepare test evidence for PRs.

Quick Start

Start by identifying changed UI files in the feature branch, then follow Phase 1 to Phase 3: review changes, assess test coverage, run MCP-driven validation, and document any gaps or new test cases.

Frequently Asked Questions about playwright-validation

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

FAQPage Schema
How do I validate UI changes in a feature branch to prevent regressions?▼

To validate UI changes in a feature branch, guide Playwright end-to-end testing to ensure new code paths are exercised and no regressions slip through. This workflow targets feature branches and PR reviews to verify visual and interactive behavior.

How do I find missing E2E test coverage for modified components?▼

Find missing E2E test coverage by analyzing existing Playwright tests for the modified components. The workflow reviews branch changes against UI tests using Playwright MCP to identify gaps and add missing testing scenarios.

What is the best way to prepare test evidence for a PR review using Playwright?▼

The best way to prepare test evidence for a PR review is to validate visual and interactive behavior across key UI flows using Playwright MCP. Execute tests and document any gaps or new test cases found during validation.

Do I need Playwright MCP integration to review branch changes against UI tests?▼

Yes, you need Playwright tooling and MCP integration to read changes, assess test coverage, execute tests, and document findings. This integration is required to drive MCP-driven validation across the modified feature branch.

Can I use this workflow to add missing test scenarios across multiple components?▼

Yes, you can add missing test scenarios across components by analyzing existing Playwright tests for modified components. The workflow enables phases from reviewing modifications to adding missing tests across components.

Related Skills

Explore More Software Engineering Skills→
yoshisadayoshisada

kiln-coverage

Enforce an 80% line and branch coverage gate for changed files.

Community
Intermediate
wesleyosantos91wesleyosantos91
6

test-gen

Generate or improve automated tests with coverage gap reports.

Community
Intermediate
Jason-Clark-FGJason-Clark-FG

playwright-validation

Validate UI changes on feature branches with Playwright end-to-end tests.

Community
Intermediate
vrcmsvrcms
1

ai-regression-testing

Generates regression tests for AI-developed web applications using Vitest.

Community
Advanced