playwright-testing

Automate end-to-end UI testing of web applications with Playwright.

1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/dappvibe/pexfi --skill playwright-testing-dappvibe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-testing
Source: https://github.com/dappvibe/pexfi/tree/main/.agent/skills/playwright-testing
Command: npx skills add https://github.com/dappvibe/pexfi --skill playwright-testing-dappvibe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @playwright/test, and includes scripts (resource) components.

What problem does it solve?

Playwright-based end-to-end testing for web applications helps teams quickly verify UI flows, catch regressions, and produce screenshots for visual validation.

Core Features & Use Cases

  • Run tests in headed mode with line reporting to observe real-time results.
  • Debug failing tests and inspect browser console logs for issues.
  • Capture screenshots to document visual regressions and verify UI states.

Quick Start

Run the Playwright test suite in headed mode to observe UI flows and capture screenshots when needed.

Frequently Asked Questions about playwright-testing

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

FAQPage Schema
How do I run Playwright tests in headed mode to debug UI flows?

To run Playwright tests in headed mode, execute the test script in a Node.js environment with Playwright installed to observe real-time UI execution and line reporting for immediate visual debugging.

Can I capture screenshots during web UI automation to verify visual regressions?

Yes, you can capture screenshots during web UI automation through an optional script feature to document visual regressions and verify UI states throughout the test execution lifecycle.

Does end-to-end testing with Playwright require a specific environment setup?

End-to-end testing with Playwright requires a Node.js environment with the @playwright/test dependency installed to properly execute test scripts and support debugging and screenshot capture.

What is the best way to debug failing E2E tests and inspect browser console logs?

The best way to debug failing E2E tests is to run Playwright in headed mode with line reporting, allowing you to observe real-time UI execution and inspect browser console logs for issues.

How do I automate test maintenance and catch UI regressions in a CI environment?

You can automate test maintenance and catch UI regressions in a CI environment by running Playwright test scripts that provide line reporting and optional screenshot capture to verify application stability.