skills.rest
stitts-dev
stitts-devCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

playwright-manual-testing-workflow

Executes manual web app testing plans with Playwright MCP, capturing screenshots and accessibility trees.

Updated Mar 4, 2026
Search Tags:#testing#manual testing#playwright#screenshot#ui validation#pr-validation
One-click install
npx skills add https://github.com/stitts-dev/dotfiles --skill playwright-manual-testing-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwright-manual-testing-workflow
Source: https://github.com/stitts-dev/dotfiles/tree/main/.claude/skills/playwright-manual-testing-workflow
Command: npx skills add https://github.com/stitts-dev/dotfiles --skill playwright-manual-testing-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines manual UI testing by providing a systematic approach to execute test plans, capture visual evidence, and document results, ensuring thorough validation before code merges.

Core Features & Use Cases

  • Systematic Test Execution: Follows a defined test plan with clear steps and expected outcomes.
  • Evidence Capture: Automatically takes screenshots of UI states and accessibility trees.
  • PR Validation: Facilitates attaching detailed test results and screenshots to pull requests.
  • Use Case: When a new feature requires visual verification, this Skill guides the tester through the scenarios, captures screenshots of each step, and helps compile a report for the PR.

Quick Start

Execute the manual testing plan for the new contribution feature, capturing screenshots for each step and updating the PR with the results.

Frequently Asked Questions about playwright-manual-testing-workflow

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

FAQPage Schema
How do I capture UI screenshots for manual testing pull request validation?▼

To capture UI screenshots for pull request validation, this Skill systematically executes your manual testing plan using the Playwright MCP plugin, taking screenshots of UI states and accessibility trees to document test results for PR validation.

What is the best way to document manual UI test results for a pull request?▼

The best way to document manual UI test results for a pull request is to execute the test plan, capture visual evidence via screenshots and accessibility trees, and compile a detailed test report to attach directly to the PR.

Do I need the Playwright MCP plugin to execute manual testing plans?▼

Yes, you need the Playwright MCP plugin to execute manual testing plans, along with a running web application, a defined test plan, and valid test data to systematically capture UI states and document results.

How does capturing accessibility trees help with UI validation?▼

Capturing accessibility trees during UI validation provides a structured representation of the UI state alongside screenshots, ensuring thorough evidence capture of the application's behavior for accurate pull request validation.

Can I use this manual testing workflow without a predefined test plan?▼

No, this manual testing workflow requires a predefined test plan with clear steps and expected outcomes, plus valid test data and a running application, to systematically guide test execution and capture evidence.

Related Skills

Explore More Software Engineering Skills→
shuyu-labsshuyu-labs
288

webapp-testing

Automate Playwright UI testing of local web applications with Python scripts.

Official
Intermediate
ByronWilliamsCPAByronWilliamsCPA

pr-review

Aggregate Copilot, SonarQube, CI, and agent findings into a tiered GitHub PR report.

Official
Advanced
bobmatnycbobmatnyc
68

screenshot

Capture desktop, tablet, and mobile screenshots for UI verification.

Community
Intermediate
bacchus-labsbacchus-labs
4

visual-regression-testing

Automate visual regression testing by comparing screenshots against baselines.

Official
Advanced