skills.rest
weval-org
weval-orgOFFICIAL
Explore all skills by this author →
WebsiteGitHub

e2e-pr

Run Playwright end-to-end tests on routes affected by pull-request changes.

31|9|Updated May 31, 2025
Search Tags:#pull request#next.js#regression#end-to-end#playwright#ui testing#route mapping
One-click install
npx skills add https://github.com/weval-org/app --skill e2e-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-pr
Source: https://github.com/weval-org/app/tree/main/.claude/skills/e2e-pr
Command: npx skills add https://github.com/weval-org/app --skill e2e-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you confirm that a pull request has not broken key user flows by running end-to-end checks against the parts of the app the change can affect.

Core Features & Use Cases

  • Route-aware test selection: Maps changed files to affected pages so you can focus testing where the UI actually changed.
  • Targeted or full-suite execution: Runs a specific Playwright spec for a route, or the entire e2e suite when shared components or layouts change.
  • Clear verification reporting: Summarizes pass or fail results, points to traces and HTML reports, and highlights any changed routes that lack coverage.
  • Use case: Before merging a branch that updates a dashboard page and a shared header, run the skill to validate the impacted routes without manually guessing what to test.

Quick Start

Ask the assistant to run the PR end-to-end checks for the changed routes and report any failures, trace links, and coverage gaps.

Frequently Asked Questions about e2e-pr

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

FAQPage Schema
How do I run Playwright end-to-end tests only for changed Next.js routes in a pull request?▼

Run end-to-end tests by mapping changed files to affected Next.js pages, layouts, and shared components. This route-aware test selection executes targeted Playwright specs for specific UI changes rather than running the entire suite blindly.

What happens if a pull request modifies a shared Next.js layout or component?▼

When a pull request modifies shared Next.js layouts or components, the end-to-end test runner escalates scope from targeted route execution to the full Playwright suite to verify all potentially impacted user flows.

Does this end-to-end testing approach identify changed routes that lack Playwright test coverage?▼

Yes, the end-to-end testing approach identifies coverage gaps by highlighting changed Next.js routes that lack Playwright specs, ensuring you know exactly where test coverage is missing before merging a pull request.

How are Playwright test failures reported for pull request UI changes?▼

Playwright test failures are reported with pass or fail summaries, direct links to HTML reports, and trace artifacts. This failure reporting provides the exact debugging context needed for the broken UI flows.

Can I verify PR UI changes in Next.js without manually guessing which routes to test?▼

Yes, you can verify pull request UI changes without guessing by using diff-based route detection. The tool automatically maps changed files to affected Next.js routes and executes the necessary end-to-end tests.

Related Skills

Explore More Software Engineering Skills→
kmshihab7878kmshihab7878
6

understand-diff

Map git diff changes to knowledge-graph nodes and write diff-overlay.json.

Community
Advanced
ABLER-Digital-ServicesABLER-Digital-Services

it-app-e2e-runner

Execute Playwright end-to-end tests and inspect failure artifacts.

Official
Intermediate
kamp-uskamp-us
25

ship-it

Automate squash merging of verified Pull Requests with green CI status.

Official
Advanced
gulati8gulati8
3

e2e-regression-testing

Generates Playwright-based end-to-end regression suites with nine-phase workflow and CI-ready artifacts.

Community
Advanced