scenario-test

Generate Playwright TypeScript end-to-end tests with TC-ID traceability.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/takimoto-sketch/medica-agent --skill scenario-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scenario-test
Source: https://github.com/takimoto-sketch/medica-agent/tree/main/.claude/skills/scenario-test
Command: npx skills add https://github.com/takimoto-sketch/medica-agent --skill scenario-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of turning manually defined test scenarios into reliable Playwright end-to-end test code by guiding design, executing interactive verification, and generating production-ready TypeScript test files with traceability and quality checks.

Core Features & Use Cases

  • Interactive scenario design: Collaboratively elicit target URL, objectives, preconditions, and prioritized test cases with the user or QA agent.
  • Manual verification with Playwright CLI: Run and record steps, capture snapshots and screenshots, and log pass/fail outcomes during exploratory validation.
  • Automated code generation and setup: Emit .spec.ts files under tests/, embed TC-IDs for traceability, apply lint fixes, run bun e2e, and suggest refactors to stabilize CI execution.
  • QA integration: Accept TC lists from a QA-management agent, preserve priority metadata, and skip redundant re‑hearing when full test case data is provided.

Quick Start

Ask the skill to design and generate Playwright E2E tests for a target site, verify them interactively, and produce runnable TypeScript spec files.

Frequently Asked Questions about scenario-test

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

FAQPage Schema
How do I generate Playwright E2E tests from manual test scenarios?

Playwright E2E test generation involves interactively designing scenarios, verifying steps with Playwright CLI, and emitting TypeScript .spec.ts files under tests/. The workflow embeds TC-IDs for QA traceability, applies lint fixes, and executes tests using bun e2e to ensure CI stability.

Can I use bun to run Playwright end-to-end tests generated from a QA-managed test case list?

Yes, generated Playwright tests are fully compatible with bun e2e execution. The workflow accepts prioritized test case lists from a QA-management agent, skips redundant re-hearing when full data is provided, and outputs .spec.ts files that run directly via bun.

What is the best way to add traceability to Playwright test code?

The best way to add traceability is to embed TC-IDs directly into generated TypeScript .spec.ts files. This workflow preserves priority metadata from QA-managed test cases, ensuring every automated Playwright test maps back to its original manual test scenario.

How do I record and verify web application flows like login and checkout before writing test code?

You can verify web application flows by running Playwright CLI for interactive recording and capturing snapshots during exploratory validation. This workflow logs pass/fail outcomes for target scenarios like login and checkout before automatically generating the final TypeScript test files.

Does this Playwright test generation workflow suggest refactors to stabilize CI execution?

Yes, the workflow applies lint fixes and suggests refactors to stabilize CI execution after generating the Playwright test files. It runs bun e2e as part of the process to validate the .spec.ts files and ensure reliable end-to-end test automation.