skills.rest
ngocsangyem
ngocsangyemCOMMUNITY
Explore all skills by this author →
𝕏@ngocsangyemGitHub

meow:qa-manual

Automate spec-driven manual QA testing and generate Playwright E2E tests.

14|2|Updated Mar 25, 2026
Search Tags:#automation#reports#qa#playwright#test-generation#e2e-testing#manual-testing
One-click install
npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-qa-manual
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: meow:qa-manual
Source: https://github.com/ngocsangyem/MeowKit/tree/main/.claude/skills/meow%3Aqa-manual
Command: npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-qa-manual

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This feature enables teams to run spec-driven manual QA tests and generate Playwright-based end-to-end tests without exposing credentials, producing structured reports or production-ready .spec.ts files.

Core Features & Use Cases

  • Orchestrates browser-based QA flows to test web apps as a human tester, collecting evidence and reporting outcomes.
  • Generates Playwright code from manual QA steps for rapid E2E automation and test coverage expansion.
  • Supports URL-based exploration and spec-driven workflows for login flows and exploratory testing.

Quick Start

Provide a spec file path or URL to start QA runs and generate outputs.

Frequently Asked Questions about meow:qa-manual

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

FAQPage Schema
How do I generate Playwright E2E tests from manual QA testing steps?▼

To generate Playwright E2E tests from manual QA steps, you provide a spec file or URL. The skill orchestrates browser-based DOM interactions as a human tester and emits production-ready .spec.ts code for rapid test coverage expansion.

Can I run spec-driven manual QA testing without exposing my login credentials?▼

Yes, you can run spec-driven manual QA testing without exposing credentials. The skill implements an auth prompt-always protocol, securely handling login flow testing and exploratory testing without embedding sensitive data in outputs.

What is the best way to automate exploratory testing from a URL?▼

The best way to automate exploratory testing from a URL is using spec-driven QA workflows. The skill navigates web apps via Playwright, collecting evidence and reporting structured QA outcomes based on the provided URL.

Does this QA testing approach produce structured reports for failed test cases?▼

Yes, this QA testing approach produces structured reports. After executing spec-driven manual tests and E2E generation, the skill emits detailed QA reports documenting outcomes and collected evidence from browser-based flows.

Do I need a spec file to start automated login flow testing?▼

You do not strictly need a spec file to start automated login flow testing. The skill supports both URL-based exploration and spec-driven workflows, allowing you to initiate testing by providing either a spec file path or a direct URL.

When should I not use Playwright for spec-driven E2E test generation?▼

You should not use Playwright for spec-driven E2E test generation if your target application lacks browser-based DOM interactions or if your testing context requires non-web protocols not supported by standard browser automation workflows.

Related Skills

Explore More Software Engineering Skills→
mikemylmikemyl
1

front-end-testing

Automate React UI component tests with Vitest Browser Mode and DOM Testing Library.

Community
Intermediate
vincehvinceh
1

playwright-testing

Create Playwright end-to-end tests with TypeScript and GitHub Actions.

Community
Advanced
devopstalesdevopstales
1

playwright

Automate Playwright browser tests and capture screenshots and traces.

Community
Intermediate
JuanMS20JuanMS20
1

e2e-testing

Automate end-to-end tests with Playwright, Cypress, or Selenium.

Community
Advanced