web-test-runner

Route user intents to case-generation or case-execution pipelines for web testing workflows.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/yy757303533/webtest-mcp-server --skill web-test-runner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-test-runner
Source: https://github.com/yy757303533/webtest-mcp-server/tree/main/.cursor/skills/web-test-runner
Command: npx skills add https://github.com/yy757303533/webtest-mcp-server --skill web-test-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

将 Web 测试从需求分析到用例生成再到执行与 HTML 报告的全流程统一入口,简化工作流并提高一致性。

Core Features & Use Cases

  • 端到端工作流编排:根据用户意图在生成用例和执行用例之间路由,确保流程一致性。
  • 需求到用例的桥接:读取并触发子技能(case-generator)将需求文档转化为可执行的测试用例。
  • 执行与报告生成:调用子技能(case-executor)执行用例并产出可交互的 HTML 报告。
  • 全流程集成示例:流程 A(生成用例)+ 流程 B(执行用例)组合,完成从需求到测试结果的端到端流水线。

Quick Start

直接告诉系统你要生成用例还是执行用例,即可开始相应流程。

Frequently Asked Questions about web-test-runner

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

FAQPage Schema
How do I orchestrate end-to-end web testing workflows from requirements?

End-to-end web testing workflows are orchestrated by routing user intents between a case-generation pipeline and a case-execution pipeline, translating requirements into Excel-based test cases and generating HTML reports.

How do I generate test cases from requirements documents?

Test case generation is handled by the case-generator sub-skill, which reads requirement documents and translates them into Excel-based test cases for subsequent execution.

Can I execute test cases and produce HTML reports automatically?

Test case execution and HTML report generation are automated by the case-executor sub-skill, which processes the generated Excel-based cases and outputs interactive HTML test reports.

Do I need specific sub-skills to run the web testing workflow?

The web testing workflow requires sub-skills located at .claude/skills/case-generator and .claude/skills/case-executor, along with a root SKILL.md frontmatter containing the name and description.

What is the best way to combine test generation and execution into one pipeline?

Combining test generation and execution involves triggering the case-generator pipeline to create Excel test cases, then invoking the case-executor pipeline to execute them and produce HTML reports.

When should I not use this approach for web testing automation?

This approach is not suitable for projects that do not utilize Excel-based test cases or require HTML reports, as the workflow specifically routes intents between Excel case generation and HTML report execution.