← ClaudeAtlas

mushi-testlisted

Run, review, and improve Mushi Mushi TDD tests — story mapping, Playwright test generation, QA coverage, PDCA improvement loop, test approval workflow. Use when "run tdd tests", "generate tests for my stories", "check qa coverage", "improve failing tests", "test my app with mushi", "review generated tests", or any TDD/QA workflow in mushi.
kensaurus/mushi-mushi · ★ 2 · Testing & QA · score 68
Install: claude install-skill kensaurus/mushi-mushi
# Mushi TDD Testing Guide ## The TDD Loop ``` Live App → map stories → generate tests → approve → run → analyze failures → improve → repeat ``` ## Step 1: Map User Stories ```bash # Automatic discovery from live app (recommended) mushi stories map --url https://your-app.com --wait # Or use the console: Inventory → Discovery → "Map from live app" ``` Review the draft in **Inventory → Discovery → Past proposals** and click **Accept**. ## Step 2: Generate Playwright Tests ```bash # From CLI (after accepting a proposal) mushi tdd gen <story-id> --mode review # Options: # --mode auto → enabled immediately, no approval needed # --mode review → lands in pending queue (default) # --no-pr → skip GitHub PR # Or via MCP in Cursor: # generate_tdd_from_story(projectId, storyNodeId, automationMode: 'review') ``` Each generated test includes: - Full TypeScript Playwright spec (`@playwright/test`) - Firecrawl Actions YAML equivalent (for cloud-only execution) - Draft GitHub PR (if configured) ## Step 3: Review and Approve ```bash # See what needs review mushi tdd pending # Approve a test (enables it in QA schedule) mushi tdd approve <qa-story-id> # Reject a test mushi tdd approve <qa-story-id> --reject ``` In the console: **QA Coverage → "TDD Tests Pending Review"** banner shows the queue. ## Step 4: Run Tests Tests run automatically on cron (default: hourly). ```bash # Trigger manually mushi tdd run <qa-story-id> # Or via MCP: run_qa_story(projectId, qaStoryId) `