{"id":"f0dea4a5-a878-4884-af86-93de58a88d9a","slug":"clawhub-kokxi-qa-test-strategy-design","name":"qa-test-strategy-design","description":"当新项目启动需要制定测试方案、或者迭代开始前需要确定\"这期怎么测\"时使用此技能。根据项目特征（新项目/迭代/重构/紧急修复）、风险分布和资源约束设计分层测试策略，明确测试范围、测试手段、准入准出标准和工具选型。一个好的测试策略让团队知道\"测什么、不测什么、为什么\"——其中\"不测什么\"往往比\"测什么\"更能体现决策质量。输出风险矩阵、分级测试方案与准入准出标准的测试策略文档。 触发场景：测试策略、怎么测、测试计划、方案设计、测试范围、质量策略、新项目启动确定测试方案时。 Use when the user asks about: test strategy for a new project or iteration — scope, layered approach, entry and exit criteria, risk matrix, and tooling.","canonicalUrl":"https://www.xpersona.co/agent/clawhub-kokxi-qa-test-strategy-design","sourceUrl":"https://clawhub.ai/kokxi/qa-test-strategy-design","homepage":"https://clawhub.ai/kokxi/skills/qa-test-strategy-design","source":"CLAWHUB","vendor":{"slug":"clawhub","label":"Clawhub","url":"https://clawhub.ai/kokxi/skills/qa-test-strategy-design"},"protocols":["OPENCLEW"],"capabilities":[],"trustScore":null,"trustConfidence":"unknown","artifactCount":0,"benchmarkCount":0,"lastRelease":"1.8.0","freshnessAt":"2026-10-11T02:12:21.323Z","freshnessLabel":"Oct 11, 2026","securityReviewed":true,"openapiReady":false,"stats":[{"label":"Trust score","value":"Unknown"},{"label":"Compatibility","value":"OpenClaw"},{"label":"Freshness","value":"Oct 11, 2026"},{"label":"Vendor","value":"Clawhub"},{"label":"Artifacts","value":"0"},{"label":"Benchmarks","value":"0"},{"label":"Last release","value":"1.8.0"}],"factsPreview":[{"factKey":"vendor","category":"vendor","label":"Vendor","value":"Clawhub","href":"https://clawhub.ai/kokxi/skills/qa-test-strategy-design","sourceUrl":"https://clawhub.ai/kokxi/skills/qa-test-strategy-design","sourceType":"profile","confidence":"medium","observedAt":"2026-10-11T02:12:21.460Z","isPublic":true},{"factKey":"protocols","category":"compatibility","label":"Protocol compatibility","value":"OpenClaw","href":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-test-strategy-design/contract","sourceUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-test-strategy-design/contract","sourceType":"contract","confidence":"medium","observedAt":"2026-10-11T02:12:21.460Z","isPublic":true},{"factKey":"traction","category":"adoption","label":"Adoption signal","value":"1.2K downloads","href":"https://clawhub.ai/kokxi/qa-test-strategy-design","sourceUrl":"https://clawhub.ai/kokxi/qa-test-strategy-design","sourceType":"profile","confidence":"medium","observedAt":"2026-10-11T02:12:21.460Z","isPublic":true},{"factKey":"latest_release","category":"release","label":"Latest release","value":"1.8.0","href":"https://clawhub.ai/kokxi/qa-test-strategy-design","sourceUrl":"https://clawhub.ai/kokxi/qa-test-strategy-design","sourceType":"release","confidence":"medium","observedAt":"2026-09-29T04:29:49.195Z","isPublic":true},{"factKey":"handshake_status","category":"security","label":"Handshake status","value":"UNKNOWN","href":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-test-strategy-design/trust","sourceUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-test-strategy-design/trust","sourceType":"trust","confidence":"medium","observedAt":null,"isPublic":true}],"highlights":["1.2K downloads","Trust evidence available"],"agentCard":{"name":"qa-test-strategy-design","description":"当新项目启动需要制定测试方案、或者迭代开始前需要确定\"这期怎么测\"时使用此技能。根据项目特征（新项目/迭代/重构/紧急修复）、风险分布和资源约束设计分层测试策略，明确测试范围、测试手段、准入准出标准和工具选型。一个好的测试策略让团队知道\"测什么、不测什么、为什么\"——其中\"不测什么\"往往比\"测什么\"更能体现决策质量。输出风险矩阵、分级测试方案与准入准出标准的测试策略文档。 触发场景：测试策略、怎么测、测试计划、方案设计、测试范围、质量策略、新项目启动确定测试方案时。 Use when the user asks about: test strategy for a new project or iteration — scope, layered approach, entry and exit criteria, risk matrix, and tooling.","source":"CLAWHUB","sourceId":"clawhub:s170jw3s1atcj5jwhqb4r7v7eh8912kp:qa-test-strategy-design","homepage":"https://clawhub.ai/kokxi/skills/qa-test-strategy-design","repository":"https://clawhub.ai/kokxi/qa-test-strategy-design","documentation":"https://www.xpersona.co/agent/clawhub-kokxi-qa-test-strategy-design","protocols":["OPENCLEW"],"examples":[{"kind":"example","language":"markdown","snippet":"**策略 ID**：STRAT-PAY-001   **关联需求**：REQ-PAY-001\n\n### 1. 项目背景      → 阶段/团队/技术栈熟悉度/工期/历史质量\n### 2. 风险分析      → 引用 RISK- ID 与等级，本技能不重算阈值\n### 3. 测试范围      → 测什么 / **不测什么** / 测到什么程度\n### 4. 分层策略      → 单元 60% / 接口 30% / E2E 10% / 探索补充\n### 5. 手段选择      → 自动化/手动/工具辅助 + 理由\n### 6. 资源分配      → 人力/时间/环境/工具\n### 7. 准入准出      → 本项目采用值 + 依据（非照抄模板）\n### 8. 风险与应对    → 环境未就绪等外部依赖的预案"},{"kind":"example","language":"text","snippet":"评估维度：\n├─ 项目阶段：新项目 / 迭代优化 / 维护阶段\n├─ 团队规模：人员数量和经验水平\n├─ 技术栈：技术复杂度和团队熟悉度\n├─ 工期：开发周期和测试周期\n└─ 历史质量：历史 Bug 密度和漏测率\n\n评估结果：\n- 项目阶段：[新项目/迭代/维护]\n- 团队：[X 人，经验水平]\n- 技术栈：[复杂度 + 团队熟悉度]\n- 工期：[开发 X 周 / 测试 Y 周]\n- 历史质量：[Bug 密度、漏测率]"}]}}