mcpField
T
team-testing

team-testing

github.com/catlog22测试与质量2.1k64 次安装19 周前更新
代码仓库

关于 team-testing

team-testing 是用于协调多 Agent 测试流程的技能,面向需要从策略制定到测试分析的开发任务。它按 L1、L2、L3 层级逐步扩展覆盖,并通过 Generator-Critic 循环收敛覆盖范围。

主要功能

  1. 01多 Agent 测试流程协调
  2. 02策略、生成、执行与分析阶段
  3. 03L1、L2、L3 分层覆盖
  4. 04Generator-Critic 覆盖循环
  5. 05任务修订与反馈

适用场景

  1. 01规划并生成分层测试
  2. 02执行测试并分析结果
  3. 03根据反馈修订测试任务

安装

复制下面的命令,在终端中运行。

$npx skills add https://github.com/catlog22/claude-code-workflow --skill team-testing

安装后在 Claude Code 中输入/team-testing确认已加载。

包含的文件

除 SKILL.md 外,安装时一起下载的参考资料和脚本。

roles/analyst/
role.md
roles/coordinator/
role.md
roles/coordinator/commands/
analyze.md
dispatch.md
monitor.md
roles/executor/
role.md
roles/generator/
role.md
roles/strategist/
role.md
specs/
pipelines.md
team-config.json

详细介绍

团队测试

编排多 Agent 测试流水线:策略制定者 -> 生成器 -> 执行器 -> 分析师。逐步覆盖各层(L1/L2/L3),通过生成器-评审者循环实现覆盖率收敛。

架构

Skill(skill="team-testing", args="task description")
                    |
         SKILL.md (this file) = Router
                    |
     +--------------+--------------+
     |                             |
  no --role flag              --role <name>
     |                             |
  Coordinator                  Worker
  roles/coordinator/role.md    roles/<name>/role.md
     |
     +-- analyze -> dispatch -> spawn workers -> STOP
                                    |
                    +-------+-------+-------+-------+
                    v       v       v       v
                [strat] [gen]  [exec]  [analyst]
                team-worker agents, each loads roles/<role>/role.md

角色注册表

角色路径前缀内部循环
协调者roles/coordinator/role.md——
策略制定者roles/strategist/role.mdSTRATEGY-*false
生成器roles/generator/role.mdTESTGEN-*true
执行器roles/executor/role.mdTESTRUN-*dynamic
分析师roles/analyst/role.mdTESTANA-*false

角色路由器

解析 $ARGUMENTS:

  • 包含 --role <name> -> 读取 roles/<name>/role.md,执行阶段 2-4
  • 不包含 --role -> @roles/coordinator/role.md,执行入口路由器

共享常量

  • 会话前缀:TST
  • 会话路径:.workflow/.team/TST-<slug>-<date>/
  • 团队名称:testing
  • CLI 工具:ccw cli --mode analysis(只读),ccw cli --mode write(修改)
  • 消息总线:mcp__ccw-tools__team_msg(session_id=<session-id>, ...)

工作线程启动模板

协调者使用此模板启动工作线程:

Agent({
  subagent_type: "team-worker",
  description: "Spawn <role> worker",
  team_name: "testing",
  name: "<role>",
  run_in_background: true,
  prompt: `## Role Assignment
role: <role>
role_spec: <skill_root>/roles/<role>/role.md
session: <session-folder>
session_id: <session-id>
team_name: testing
requirement: <task-description>
inner_loop: <true|false>

## Progress Milestones
session_id: <session-id>
Report progress via team_msg at natural phase boundaries (context loaded -> core work done -> verification).
Report blockers immediately via team_msg type="blocker".
Report completion via team_msg type="task_complete" after final SendMessage.

Read role_spec file (@<skill_root>/roles/<role>/role.md) to load Phase 2-4 domain instructions.
Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5 (report).`
})

用户命令

命令操作
check / status查看流水线状态图
resume / continue进入下一步
revise <TASK-ID>修改指定任务
feedback <text>注入反馈以进行修改

完成操作

流水线完成后,协调者将展示:

AskUserQuestion({
  questions: [{
    question: "Testing pipeline complete. What would you like to do?",
    header: "Completion",
    multiSelect: false,
    options: [
      { label: "Archive & Clean (Recommended)", description: "Archive session, clean up team" },
      { label: "Keep Active", description: "Keep session for follow-up work" },
      { label: "Deepen Coverage", description: "Add more test layers or increase coverage targets" }
    ]
  }]
})

会话目录

.workflow/.team/TST-<slug>-<date>/
├── .msg/messages.jsonl     # Team message bus
├── .msg/meta.json          # Session metadata
├── wisdom/                 # Cross-task knowledge
├── strategy/               # Strategist output
├── tests/                  # Generator output (L1-unit/, L2-integration/, L3-e2e/)
├── results/                # Executor output
└── analysis/               # Analyst output

规范参考

错误处理

场景解决方案
未知的 --role 值报错并列出可用角色
找不到角色报错并显示预期路径(roles//role.md)
CLI 工具失败工作线程回退到直接实现
GC 循环超限发出警告并接受当前覆盖率
快速推进冲突协调者在下次回调时协调处理
完成操作失败默认设为保持活动状态

评论

支持 Markdown