qa-create

Generate Playwright QA tests for MulmoCast with verified DOM selectors.

41|11|Updated May 22, 2025
One-click install
npx skills add https://github.com/receptron/mulmocast-app --skill qa-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-create
Source: https://github.com/receptron/mulmocast-app/tree/main/.claude/skills/qa-create
Command: npx skills add https://github.com/receptron/mulmocast-app --skill qa-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly produces a structured QA test suite for MulmoCast by translating the project’s QA playbook and an existing testing baseline into concrete CDP-driven Playwright tests.

Core Features & Use Cases

  • Playbook-guided test design: Follows the playbook’s Phase structure (Setup → Core Feature → Integration → Health) to ensure consistent coverage.
  • Bidirectional UI/JSON validation: Includes both UI → JSON and JSON → UI checks to catch integration and state-mapping regressions.
  • Deterministic, verified selectors: Requires inspecting the real DOM first and only uses stable selectors (e.g., data-testid/data-slot/accessible roles) to prevent brittle tests.
  • Execution gate with fixes: Mandates running at least one generated test before completion, then iterating on failures until success.

Quick Start

Ask the QA system to generate a new Playwright CDP-based QA test suite for a specific MulmoCast feature, including any relevant preconditions and whether external API calls should be considered.

Frequently Asked Questions about qa-create

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

FAQPage Schema
How do I generate a Playwright test suite that maps UI state to JSON correctly?

This system generates a Playwright test suite mapping UI state to JSON by applying the project QA playbook patterns and existing test baseline. It creates phase-based tests covering Setup, Core Feature, Integration, and Health scenarios with bidirectional UI/JSON validation.

Why do my generated Playwright tests fail due to brittle selectors?

Playwright tests fail due to brittle selectors when using unstable DOM attributes. This system prevents brittle tests by requiring mandatory real DOM selector verification via an mcp-pw task delegation, ensuring only stable selectors like data-testid or accessible roles are used.

Can I use Electron and CDP for UI-JSON testing with Playwright?

You can use Electron and CDP for UI-JSON testing with Playwright. This system generates CDP-driven Playwright tests specifically designed for targeted UI and integration scenarios where UI state must map correctly to JSON and vice versa across defined test phases.

What is the best way to structure a QA test suite for consistent coverage?

The best way to structure a QA test suite for consistent coverage is following a phase-based design. This system applies the playbook's phase structure of Setup, Core Feature, Integration, and Health phases to ensure organized and comprehensive test coverage.

How do I verify selectors against the real DOM before running Playwright tests?

To verify selectors against the real DOM before running Playwright tests, this system performs mandatory real DOM selector verification via an mcp-pw task delegation. It inspects the real DOM first and only uses stable selectors to prevent brittle tests.

Does the generated test suite need to pass before updating the QA documentation?

The generated test suite must pass before updating QA documentation. The system mandates running at least one generated test successfully and iterating on failures until success, then updating test/README.md and docs/qa_playbook.md.