skills.rest
divad12
divad12COMMUNITY
Explore all skills by this author →
WebsiteGitHub

qa-test

Automate browser-based end-to-end UI testing with Playwright MCP and report PASS/FAIL/CONCERN per scenario.

25|4|Updated Sep 5, 2010
Search Tags:#automation#testing#qa#end-to-end#playwright#ui-testing#browser
One-click install
npx skills add https://github.com/divad12/dotfiles --skill qa-test-divad12
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-test
Source: https://github.com/divad12/dotfiles/tree/main/.claude/skills/qa-test
Command: npx skills add https://github.com/divad12/dotfiles --skill qa-test-divad12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Launch a browser-only QA tester that tests the running app like a real user. The agent has no access to source code - it can only see and interact with the browser via Playwright MCP. It reports PASS/FAIL/CONCERN per scenario.

Core Features & Use Cases

  • End-to-end UI testing: validate real user flows against the live app
  • No source access: tester cannot inspect source code, only browser behavior
  • Scenario-based reporting: outputs per-scenario PASS/FAIL/CONCERN

Quick Start

Launch the browser-only QA tester against the running application to begin end-to-end validation.

Frequently Asked Questions about qa-test

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

FAQPage Schema
How do I automate end-to-end UI testing for a live application?▼

You can automate end-to-end UI testing by launching a browser-only QA tester that interacts with your running app via Playwright, validating real user flows without source code access and reporting PASS/FAIL/CONCERN per scenario.

Can I run regression checks without giving the tester access to my source code?▼

Yes, you can run regression checks without source access because the tester operates browser-only, seeing and interacting solely with browser behavior to validate scenarios against the live application.

Does this QA tester use Playwright for browser automation?▼

Yes, this QA tester uses Playwright MCP for browser automation, driving end-to-end UI tests against complex user flows to report per-scenario PASS/FAIL/CONCERN outcomes.

What do I need to set up before running scenario-driven end-to-end tests?▼

You need a running application accessible to the tester before running scenario-driven end-to-end tests, as the browser-only QA agent validates live UI behavior without local source code access.

What are the limitations of a browser-only approach to end-to-end UI testing?▼

The limitation of a browser-only approach is that the tester cannot inspect source code; it can only see and interact with browser behavior, which may restrict debugging to visible UI interactions.

Related Skills

Explore More Software Engineering Skills→
The13thNodeThe13thNode
3

browse

Launch a real browser to verify application UI and functionality.

Community
Intermediate
brianoniealbrianonieal

validate

Validate Syntaris harness integrity and user-project test health.

Community
Advanced
iani-kuliiani-kuli

webapp-testing

Automate local web app testing with Playwright and server management scripts.

Community
Intermediate
zangxin75zangxin75

ui-testing

Write Cypress and Testing Library tests for web UI components.

Community
Advanced