testing

Automate Playwright-based UI tests with structured test plans and diagnostics.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/shahmirerror/gsdcp-mobile --skill testing-shahmirerror
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/shahmirerror/gsdcp-mobile/tree/main/.local/skills/testing
Command: npx skills add https://github.com/shahmirerror/gsdcp-mobile --skill testing-shahmirerror

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running automated Playwright-based UI tests to verify feature correctness across a live app, saving time on regression checks.

Core Features & Use Cases

  • End-to-end UI testing: validate interactions, navigation, and visual states in a real browser.
  • Comprehensive feedback: capture screenshots and detailed diagnostics from both frontend and backend logs.
  • Test plan driven: use structured test plans to describe user flows and expected outcomes.

Quick Start

Create a testPlan describing the user flow and call runTest with that plan

Frequently Asked Questions about testing

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

FAQPage Schema
How do I automate end-to-end UI tests with Playwright?

To automate end-to-end UI tests with Playwright, create a structured test plan describing user flows and expected outcomes, then trigger the test execution to validate frontend and backend interactions in a real browser.

What is the best way to capture screenshots and diagnostics during Playwright UI testing?

The best way to capture screenshots and detailed diagnostics during Playwright UI testing is to run a structured test plan that automatically collects frontend and backend logs to verify feature correctness.

Can I validate frontend and backend interactions in a single end-to-end test?

Yes, you can validate frontend and backend interactions in a single end-to-end test by applying a test-plan-driven approach that automates real browser flows and captures comprehensive diagnostics.

Do I need a structured test plan to run Playwright e2e validation?

Yes, you need a structured test plan to run Playwright e2e validation because the test plan describes the user flows and expected outcomes required to verify feature correctness across the live app.

How does test-plan-driven automation help with regression checks?

Test-plan-driven automation helps with regression checks by running structured Playwright UI tests against a live app, capturing screenshots and detailed diagnostics to quickly verify feature correctness and save time.