{"id":"6e3bece0-8f25-49c0-a7e8-66b745a5c4f6","entityType":"agent","slug":"clawhub-kokxi-qa-test-automation-arch","name":"qa-test-automation-arch","canonicalUrl":"https://www.xpersona.co/agent/clawhub-kokxi-qa-test-automation-arch","canonicalPath":"/agent/clawhub-kokxi-qa-test-automation-arch","generatedAt":"2026-10-11T05:32:27.538Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T03:09:25.017Z","emptyReason":null},"description":"当需要设计自动化测试框架、或者现有框架维护成本太高需要重构时使用此技能。运用 PageObject、分层测试、关键字驱动、数据驱动等模式设计可维护可扩展的自动化架构。不要直接写测试代码——先设计架构：选型（UI/API/单元）、分层（测试层/业务层/基础设施层）、数据管理（测试数据与脚本分离）和 CI 集成方案。好的自动化架构应该让写用例的人不需要懂底层实现。 触发场景：自动化架构、框架设计、自动化策略、自动化框架、测试框架架构、自动化维护困难需要重构时。 Use when the user asks about: test automation architecture — Page Object, layered test design, keyword-driven and data-driven frameworks, and data management. Skill: qa-test-automation-arch Owner: kokxi Summary: 当需要设计自动化测试框架、或者现有框架维护成本太高需要重构时使用此技能。运用 PageObject、分层测试、关键字驱动、数据驱动等模式设计可维护可扩展的自动化架构。不要直接写测试代码——先设计架构：选型（UI/API/单元）、分层（测试层/业务层/基础设施层）、数据管理（测试数据与脚本分离）和 CI 集成方案。好的自动化架构应该让写用例的人不需要懂底层实现。 触发场景：自动化架构、框架设计、自动化策略、自动化框架、测试框架架构、自动化维护困难需要重构时。 Use when the user asks about: test automation architecture — Page Object, layered test design, keyword-driven and data-driven frameworks","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s170jw3s1atcj5jwhqb4r7v7eh8912kp:qa-test-automation-arch","sourceUrl":"https://clawhub.ai/kokxi/qa-test-automation-arch","homepage":"https://clawhub.ai/kokxi/skills/qa-test-automation-arch","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/kokxi/qa-test-automation-arch","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/kokxi/skills/qa-test-automation-arch","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":61,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"当需要设计自动化测试框架、或者现有框架维护成本太高需要重构时使用此技能。运用 PageObject、分层测试、关键字驱动、数据驱动等模式设计可维护可扩展的自动化架构。不要直接写测试代码——先设计架构：选型（UI/API/单元）、分层（测试层/业务层/基础设施层）、数据管理（测试数据与脚本分离）和 CI 集成方案。好的自"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T03:09:25.017Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T03:09:25.017Z","emptyReason":null},"stars":null,"forks":null,"downloads":1177,"packageName":null,"latestVersion":"1.8.0","tractionLabel":"1.2K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T03:09:24.948Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T03:09:25.017Z","lastCrawledAt":"2026-10-11T03:09:24.948Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T03:09:24.948Z","lastVerifiedAt":null,"highlights":[{"version":"1.8.0","createdAt":"2026-09-29T04:29:06.140Z","changelog":"Version 1.8.0 - Major refactor: Layered architecture content moved to references/layered-architecture.md for better modularity and to reduce context bloat. - SKILL.md simplified to reference external architecture details, with loading instructions for when to consult the architecture file. - Skill metadata refactored and enriched for clarity and automation; previous skill-card.md removed. - Other skill documentation and structural patterns remain unchanged.","fileCount":4,"zipByteSize":5939},{"version":"1.7.7","createdAt":"2026-09-27T14:42:29.624Z","changelog":"1.7.7","fileCount":3,"zipByteSize":5295},{"version":"1.7.6","createdAt":"2026-09-01T12:47:39.368Z","changelog":"显示名改中文","fileCount":3,"zipByteSize":5604},{"version":"1.7.5","createdAt":"2026-08-30T15:20:24.487Z","changelog":"1.7.5: 版本号升级","fileCount":3,"zipByteSize":5386},{"version":"1.7.0","createdAt":"2026-08-16T14:33:13.608Z","changelog":"- Removed redundant file skill-card.md for streamlined maintenance. - Updated version to 1.7.0 in SKILL.md. - No user-facing functional or content changes in the main documentation.","fileCount":3,"zipByteSize":5075},{"version":"1.6.3","createdAt":"2026-08-12T15:29:22.501Z","changelog":"- Added \"slug\" and \"displayName\" fields to SKILL.md for improved metadata consistency. - Updated version number to 1.6.3. - Removed the file skill-card.md. - No functional or logic changes to the architecture guidance content.","fileCount":3,"zipByteSize":5039},{"version":"1.6.0","createdAt":"2026-07-06T17:18:23.794Z","changelog":"Version 1.6.0 (qa-test-automation-arch) - Added new traceability requirement: each architecture now includes a unique ARCH-XXXX ID. - Expanded related skills with qa-mobile-testing and qa-tech-debt-management. - Introduced error recovery guidance for architecture omission and retry scenarios. - Added categories and quantification guidance for architecture depth/coverage. - Updated when_to_use trigger to include \"测试框架架构\". - Removed obsolete skill-card.md file.","fileCount":3,"zipByteSize":5278},{"version":"1.5.0","createdAt":"2026-06-29T12:36:21.631Z","changelog":"- 改进描述，强调先设计架构而非直接写测试代码，增加实际最佳实践建议。 - 新增 version 字段，结构化 input_format 与 output_format，明确输入输出格式和内容。 - 强调“让用例开发者不需要懂底层实现”的设计理念。 - 为“自动化金字塔”部分增加与 qa-test-strategy-design 的概念区分说明，避免歧义。 - 删除 skill-card.md，精简文档内容结构。","fileCount":3,"zipByteSize":4653}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s170jw3s1atcj5jwhqb4r7v7eh8912kp:qa-test-automation-arch","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-test-automation-arch/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-test-automation-arch/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-test-automation-arch/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-test-automation-arch/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-test-automation-arch/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-test-automation-arch/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T05:32:27.537Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-test-automation-arch/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-test-automation-arch/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-test-automation-arch/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-test-automation-arch/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T03:09:25.017Z","emptyReason":null},"readme":"Skill: qa-test-automation-arch\n\nOwner: kokxi\n\nSummary: 当需要设计自动化测试框架、或者现有框架维护成本太高需要重构时使用此技能。运用 PageObject、分层测试、关键字驱动、数据驱动等模式设计可维护可扩展的自动化架构。不要直接写测试代码——先设计架构：选型（UI/API/单元）、分层（测试层/业务层/基础设施层）、数据管理（测试数据与脚本分离）和 CI 集成方案。好的自动化架构应该让写用例的人不需要懂底层实现。 触发场景：自动化架构、框架设计、自动化策略、自动化框架、测试框架架构、自动化维护困难需要重构时。 Use when the user asks about: test automation architecture — Page Object, layered test design, keyword-driven and data-driven frameworks, and data management.\n\nTags: latest:1.8.0\n\nVersion history:\n\nv1.8.0 | 2026-09-29T04:29:06.140Z | auto\n\nVersion 1.8.0\n\n- Major refactor: Layered architecture content moved to references/layered-architecture.md for better modularity and to reduce context bloat.\n- SKILL.md simplified to reference external architecture details, with loading instructions for when to consult the architecture file.\n- Skill metadata refactored and enriched for clarity and automation; previous skill-card.md removed.\n- Other skill documentation and structural patterns remain unchanged.\n\nv1.7.7 | 2026-09-27T14:42:29.624Z | user\n\n1.7.7\n\nv1.7.6 | 2026-09-01T12:47:39.368Z | user\n\n显示名改中文\n\nv1.7.5 | 2026-08-30T15:20:24.487Z | user\n\n1.7.5: 版本号升级\n\nv1.7.0 | 2026-08-16T14:33:13.608Z | auto\n\n- Removed redundant file skill-card.md for streamlined maintenance.\n- Updated version to 1.7.0 in SKILL.md.\n- No user-facing functional or content changes in the main documentation.\n\nv1.6.3 | 2026-08-12T15:29:22.501Z | auto\n\n- Added \"slug\" and \"displayName\" fields to SKILL.md for improved metadata consistency.\n- Updated version number to 1.6.3.\n- Removed the file skill-card.md.\n- No functional or logic changes to the architecture guidance content.\n\nv1.6.0 | 2026-07-06T17:18:23.794Z | auto\n\nVersion 1.6.0 (qa-test-automation-arch)\n\n- Added new traceability requirement: each architecture now includes a unique ARCH-XXXX ID.\n- Expanded related skills with qa-mobile-testing and qa-tech-debt-management.\n- Introduced error recovery guidance for architecture omission and retry scenarios.\n- Added categories and quantification guidance for architecture depth/coverage.\n- Updated when_to_use trigger to include \"测试框架架构\".\n- Removed obsolete skill-card.md file.\n\nv1.5.0 | 2026-06-29T12:36:21.631Z | auto\n\n- 改进描述，强调先设计架构而非直接写测试代码，增加实际最佳实践建议。\n- 新增 version 字段，结构化 input_format 与 output_format，明确输入输出格式和内容。\n- 强调“让用例开发者不需要懂底层实现”的设计理念。\n- 为“自动化金字塔”部分增加与 qa-test-strategy-design 的概念区分说明，避免歧义。\n- 删除 skill-card.md，精简文档内容结构。\n\nv1.4.1 | 2026-06-25T16:57:16.135Z | auto\n\n- Condensed the skill description for clarity and focus.\n- Removed redundant details and simplified usage instructions.\n- Deleted the skill-card.md file to streamline documentation.\n- No changes to core architecture guidance or technical content.\n\nv1.4.0 | 2026-06-24T05:13:12.771Z | auto\n\n- Expanded keywords and usage scenarios in the SKILL.md description for broader triggering and discoverability.\n- Updated the \"when_to_use\" field to include more relevant user phrases.\n- Minor improvements to description formatting and keyword coverage.\n- Removed skill-card.md for simplified skill documentation management.\n\nv1.3.0 | 2026-06-23T10:50:49.473Z | auto\n\n- 全面改写：技能文档重构并详细阐述自动化测试架构设计原则与分层策略。\n- 新增测试自动化金字塔分层说明，明确单元、集成、E2E各层职责及最佳实践。\n- 增加主流技术选型建议（含多语言方案），并细化对应测试层工具。\n- 详列Page Object、关键字驱动、数据驱动等常见框架模式及其优劣。\n- 补充框架选型对比表和自动化项目实用案例。\n- 明确输入输出格式及上下游关联技能，方便与其他测试流程集成。\n\nArchive index:\n\nArchive v1.8.0: 4 files, 5939 bytes\n\nFiles: references/layered-architecture.md (1870b), skill-card.md (1825b), SKILL.md (7111b), _meta.json (142b)\n\nFile v1.8.0:SKILL.md\n\n---\nname: qa-test-automation-arch\ndescription: >-\n 当需要设计自动化测试框架、或者现有框架维护成本太高需要重构时使用此技能。运用 PageObject、分层测试、关键字驱动、数据驱动等模式设计可维护可扩展的自动化架构。不要直接写测试代码——先设计架构：选型（UI/API/单元）、分层（测试层/业务层/基础设施层）、数据管理（测试数据与脚本分离）和 CI 集成方案。好的自动化架构应该让写用例的人不需要懂底层实现。 触发场景：自动化架构、框架设计、自动化策略、自动化框架、测试框架架构、自动化维护困难需要重构时。 Use when the user asks about: test automation architecture — Page Object, layered test design, keyword-driven and data-driven frameworks, and data management.\nlicense: MIT\nallowed-tools: Read Grep Glob Bash\nmetadata:\n display-name: \"Test Automation Arch\"\n version: \"1.8.0\"\n when-to-use: \"用户说\\\"自动化架构\\\"、\\\"框架设计\\\"、\\\"自动化策略\\\"、\\\"自动化框架\\\"、\\\"测试框架架构\\\"、需要设计测试自动化架构、自动化维护困难需要重构时\"\n related-skills: \"{\\\"upstream\\\":[\\\"qa-tech-selection\\\",\\\"qa-test-strategy-design\\\"],\\\"downstream\\\":[\\\"qa-ci-cd-testing\\\",\\\"qa-api-testing\\\",\\\"qa-mobile-testing\\\",\\\"qa-tech-debt-management\\\"]}\"\n references: \"[\\\"references/layered-architecture.md\\\"]\"\n input-format: \"{\\\"required\\\":[{\\\"name\\\":\\\"测试策略\\\",\\\"type\\\":\\\"object\\\",\\\"description\\\":\\\"来自qa-test-strategy-design的测试策略\\\"},{\\\"name\\\":\\\"技术选型\\\",\\\"type\\\":\\\"object\\\",\\\"description\\\":\\\"来自qa-tech-selection的技术选型建议\\\"}],\\\"optional\\\":[{\\\"name\\\":\\\"项目约束\\\",\\\"type\\\":\\\"string\\\",\\\"description\\\":\\\"技术栈和团队限制\\\"}]}\"\n output-format: \"{\\\"traceability\\\":[\\\"每份架构设计带唯一ID（ARCH-XXXX）\\\"],\\\"structure\\\":[\\\"覆盖率：标注口径（基于现有需求/输入文档），禁止\\\\\\\"全覆盖/100%\\\\\\\"绝对化表述；缺失模块标注\\\\\\\"未覆盖+原因\\\\\\\"\\\",{\\\"automation_architecture\\\":\\\"自动化测试架构设计\\\"},{\\\"framework_selection\\\":\\\"框架选择建议\\\"},{\\\"layer_design\\\":\\\"分层设计\\\"},{\\\"maintenance_strategy\\\":\\\"维护策略\\\"}]}\"\n error-recovery-guidance: \"{\\\"on_failure\\\":\\\"自动化架构遗漏维护策略时回退到技术选型补充\\\",\\\"retry_behavior\\\":\\\"补充选型后重新设计架构\\\"}\"\n categories: \"[\\\"Development\\\",\\\"Testing\\\",\\\"DevOps\\\"]\"\n depth-requirement: \"{\\\"reference_value\\\":\\\"根据架构复杂度调整设计深度：简单×1/中等×2/复杂×3\\\",\\\"minimum\\\":\\\"至少覆盖层架构、工具集成、维护策略3个核心要素\\\"}\"\n---\n> ⚠️ 本技能单独使用效果有限，建议配合完整技能集（12 步工作流）使用。安装：npx skills add Kokxi/qa-test-skills\n\n> **⚠️ 安全警告**：本技能的示例可能涉及订单号、支付金额、截图、身份证、手机号等敏感数据。\n> 实际使用时请勿粘贴真实生产数据、客户信息或财务凭证；测试前应脱敏/掩码处理。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 测试自动化架构设计\n\n## 核心原则\n\n好的自动化架构——分层清晰、职责单一、易于维护、快速反馈。\n\n## 测试自动化金字塔\n\n> 📌 本节与 qa-test-strategy-design「测试金字塔」概念对应，但分层名称和比例不同——本技能侧重自动化落地（集成测试层名、70/20/10 比例），strategy-design 侧重策略规划（接口测试层名、60/30/10 比例）。修改时请确认两处含义，避免矛盾。\n\n```text\n ┌─────────────┐\n │ E2E测试 │ 10%\n │ (UI/API) │\n ├─────────────┤\n │ 集成测试 │ 20%\n │ (接口/服务) │\n ├─────────────┤\n │ 单元测试 │ 70%\n │ (函数/类) │\n └─────────────┘\n```\n\n## 加载时机\n\n| 什么时候读 | 读哪个 |\n|-----------|--------|\n| 设计自动化框架分层时 | [`references/layered-architecture.md`](references/layered-architecture.md) |\n\n> `分层架构设计`的完整内容已下沉至 `references/layered-architecture.md`，避免每次触发都占用上下文。\n\n## 框架设计模式\n\n### Page Object Model\n\n```text\n优点：\n├─ 封装页面元素和操作\n├─ 减少代码重复\n├─ 易于维护\n└─ 可读性强\n\n示例结构：\ntests/\n├── pages/\n│ ├── login_page.py\n│ ├── home_page.py\n│ └── cart_page.py\n├── tests/\n│ ├── test_login.py\n│ ├── test_home.py\n│ └── test_cart.py\n├── fixtures/\n│ ├── test_data.py\n│ └── setup_teardown.py\n└── utils/\n ├── driver_factory.py\n └── report_generator.py\n```\n\n### 关键字驱动\n\n```text\n优点：\n├─ 业务人员可参与\n├─ 测试用例可读性强\n├─ 与实现分离\n└─ 易于复用\n\n示例：\n| 关键字 | 参数1 | 参数2 | 参数3 |\n|--------|-------|-------|-------|\n| 打开浏览器 | Chrome | | |\n| 输入用户名 | testuser | | |\n| 输入密码 | Test@123 | | |\n| 点击登录 | | | |\n| 验证跳转 | /home | | |\n```\n\n### 数据驱动\n\n```text\n优点：\n├─ 测试数据与逻辑分离\n├─ 易于添加新用例\n├─ 覆盖多种场景\n└─ 便于维护\n\n示例：\n@pytest.mark.parametrize(\"username,password,expected\", [\n (\"user1\", \"pass1\", \"success\"),\n (\"user2\", \"pass2\", \"success\"),\n (\"\", \"pass3\", \"error\"),\n (\"user4\", \"\", \"error\"),\n])\ndef test_login(username, password, expected):\n result = login(username, password)\n assert result == expected\n```\n\n## 框架选型决策\n\n| 维度 | Playwright | Cypress | Selenium |\n|------|-----------|---------|----------|\n| 浏览器支持 | 多浏览器 | 仅Chrome | 多语言 |\n| 执行速度 | 快 | 快 | 中等 |\n| 调试体验 | 好 | 优秀 | 一般 |\n| 学习曲线 | 中等 | 低 | 高 |\n| 社区生态 | 成长中 | 成熟 | 成熟 |\n| 适用场景 | 现代Web | 单页应用 | 传统Web |\n\n## 输出示例\n\n**设计Web UI自动化框架（团队5人，JS技术栈，1000+用例）**\n→ 分层：单元测试（Jest）→集成测试（Supertest）→E2E（Playwright）\n→ 模式：Page Object Model组织页面对象，关键字驱动封装业务操作\n→ 数据驱动：JSON/CSV管理测试数据，和环境配置分离\n→ CI/CD集成：GitHub Actions触发，Allure报告\n\n**API自动化框架设计**\n→ 分层：请求封装层→业务接口层→用例层→数据层\n\n## 检查清单\n\n架构设计完成后检查：\n- [ ] 分层是否清晰（单元/集成/E2E）？\n- [ ] 各层职责是否明确？\n- [ ] 框架选型是否合理？\n- [ ] 设计模式是否适用？\n- [ ] 可维护性是否考虑？\n- [ ] CI/CD集成是否规划？\n\nFile v1.8.0:_meta.json\n\n{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-test-automation-arch\",\n \"version\": \"1.8.0\",\n \"publishedAt\": 1790656146140\n}\n\nFile v1.8.0:references/layered-architecture.md\n\n# 测试分层架构设计详解\n\n> 本文是 `qa-test-automation-arch` 的**测试分层架构设计详解**。设计自动化框架分层时读本文；\n其余部分留在 SKILL.md，不必读本文。\n\n---\n\n\n### 第1层：单元测试层\n\n```text\n职责：\n├─ 测试范围：函数、类、模块\n├─ 执行速度：毫秒级\n├─ 维护成本：低\n└─ 覆盖目标：核心逻辑\n\n技术选型：\n├─ Java：JUnit 5 + Mockito\n├─ Python：Pytest + Mock\n├─ JavaScript：Jest + Sinon\n└─ Go：testing + testify\n\n最佳实践：\n├─ 测试与代码同步维护\n├─ 每个测试单一职责\n├─ 使用Mock隔离依赖\n├─ 测试命名清晰（Given-When-Then）\n└─ 保持测试快速（<100ms）\n```\n\n### 第2层：集成测试层\n\n```text\n职责：\n├─ 测试范围：接口、服务间交互\n├─ 执行速度：秒级\n├─ 维护成本：中\n└─ 覆盖目标：业务流程\n\n技术选型：\n├─ API测试：Postman/Newman/REST Assured\n├─ 数据库测试：TestContainers\n├─ 消息队列测试：Embedded Kafka\n└─ 服务虚拟化：WireMock/Mountebank\n\n最佳实践：\n├─ 使用真实依赖（TestContainers）\n├─ 测试数据可构造、可清理\n├─ 验证接口契约\n├─ 覆盖正常/异常/边界场景\n└─ 保持测试独立性\n```\n\n### 第3层：E2E测试层\n\n```text\n职责：\n├─ 测试范围：完整用户流程\n├─ 执行速度：分钟级\n├─ 维护成本：高\n└─ 覆盖目标：核心路径\n\n技术选型：\n├─ Web UI：Playwright/Cypress/Selenium\n├─ 移动端：Appium/XCUITest/Espresso\n├─ 桌面端：Electron Test/WinAppDriver\n└─ 性能：JMeter/Locust/k6\n\n最佳实践：\n├─ 只覆盖核心路径（20%）\n├─ 使用Page Object模式\n├─ 数据驱动测试\n├─ 稳定的等待策略\n└─ 失败时自动截图/录屏\n```\n\nFile v1.8.0:skill-card.md\n\n## Description:\n\nHelps QA engineers design maintainable test automation architectures with layered tests, framework selection, data management, and CI integration.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nQA engineers and developers use this skill to plan or refactor automated testing frameworks before writing tests. It guides test-layer design, framework selection, test-data separation, maintenance, and CI integration.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The suggested unpinned installation command may fetch an unreviewed release.\n\nMitigation: Review its source and pin a vetted version before running the command.\n\nRisk: Real customer, identity, payment, or screenshot data may be exposed when supplied to the workflow.\n\nMitigation: Use synthetic test data or mask sensitive information before sharing inputs.\n\n## Reference(s):\n\n- [Layered test architecture](references/layered-architecture.md)\n- [ClawHub skill release](https://clawhub.ai/kokxi/skills/qa-test-automation-arch)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Markdown]\n\n**Output Format:** [Markdown architecture plan]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Architecture ID (ARCH-XXXX); framework selection, layered design, and maintenance strategy; coverage claims scoped to supplied requirements.]\n\n## Skill Version(s):\n\n1.8.0 (source: skill frontmatter and server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.7.7: 3 files, 5295 bytes\n\nFiles: skill-card.md (1854b), SKILL.md (8337b), _meta.json (142b)\n\nFile v1.7.7:SKILL.md\n\n---\nname: qa-test-automation-arch\nslug: qa-test-automation-arch\ndisplayName: Test Automation Arch\nversion: 1.7.7\ndescription: >-\n 当需要设计自动化测试框架、或者现有框架维护成本太高需要重构时使用此技能。运用 PageObject、分层测试、关键字驱动、数据驱动等模式设计可维护可扩展的自动化架构。不要直接写测试代码——先设计架构：选型（UI/API/单元）、分层（测试层/业务层/基础设施层）、数据管理（测试数据与脚本分离）和 CI 集成方案。好的自动化架构应该让写用例的人不需要懂底层实现。\n\nwhen_to_use: 用户说\"自动化架构\"、\"框架设计\"、\"自动化策略\"、\"自动化框架\"、\"测试框架架构\"、需要设计测试自动化架构、自动化维护困难需要重构时\nallowed-tools: Read Grep Glob Bash\nrelated_skills:\n upstream:\n - qa-tech-selection # 输入：技术选型结果\n - qa-test-strategy-design # 输入：测试策略\n downstream:\n - qa-ci-cd-testing # 输出：架构设计用于CI/CD集成\n - qa-api-testing # 输出：架构设计指导API测试\n - qa-mobile-testing\n - qa-tech-debt-management\ninput_format:\n required:\n - name: 测试策略\n type: object\n description: 来自qa-test-strategy-design的测试策略\n - name: 技术选型\n type: object\n description: 来自qa-tech-selection的技术选型建议\n optional:\n - name: 项目约束\n type: string\n description: 技术栈和团队限制\noutput_format:\n traceability:\n - 每份架构设计带唯一ID（ARCH-XXXX）\n structure:\n - 测试用例表格：固定 9 列（用例编号|测试类型|功能模块|测试标题|用例级别|预置条件|测试步骤|预期结果|风险等级）\n - 用例级别：P0≤20%（核心流程）/ P1≤40%（主要功能）/ P2≤30%（次要功能）/ P3≤10%（边缘场景）\n - 覆盖率：标注口径（基于现有需求/输入文档），禁止\"全覆盖/100%\"绝对化表述；缺失模块标注\"未覆盖+原因\"\n - automation_architecture: 自动化测试架构设计\n - framework_selection: 框架选择建议\n - layer_design: 分层设计\n - maintenance_strategy: 维护策略\ncategories: ['Development','Testing','DevOps']\ndepth_requirement_quantification:\n reference_value: \"根据架构复杂度调整设计深度：简单×1/中等×2/复杂×3\"\n minimum: \"至少覆盖层架构、工具集成、维护策略3个核心要素\"\nerror_recovery_guidance:\n on_failure: \"自动化架构遗漏维护策略时回退到技术选型补充\"\n retry_behavior: \"补充选型后重新设计架构\"\n---\n> **⚠️ 安全警告**：本技能的示例可能涉及订单号、支付金额、截图、身份证、手机号等敏感数据。\n> 实际使用时请勿粘贴真实生产数据、客户信息或财务凭证；测试前应脱敏/掩码处理。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 测试自动化架构设计\n\n## 核心原则\n\n好的自动化架构——分层清晰、职责单一、易于维护、快速反馈。\n\n## 测试自动化金字塔\n\n> 📌 本节与 qa-test-strategy-design「测试金字塔」概念对应，但分层名称和比例不同——本技能侧重自动化落地（集成测试层名、70/20/10 比例），strategy-design 侧重策略规划（接口测试层名、60/30/10 比例）。修改时请确认两处含义，避免矛盾。\n\n```text\n ┌─────────────┐\n │ E2E测试 │ 10%\n │ (UI/API) │\n ├─────────────┤\n │ 集成测试 │ 20%\n │ (接口/服务) │\n ├─────────────┤\n │ 单元测试 │ 70%\n │ (函数/类) │\n └─────────────┘\n```\n\n## 分层架构设计\n\n### 第1层：单元测试层\n\n```text\n职责：\n├─ 测试范围：函数、类、模块\n├─ 执行速度：毫秒级\n├─ 维护成本：低\n└─ 覆盖目标：核心逻辑\n\n技术选型：\n├─ Java：JUnit 5 + Mockito\n├─ Python：Pytest + Mock\n├─ JavaScript：Jest + Sinon\n└─ Go：testing + testify\n\n最佳实践：\n├─ 测试与代码同步维护\n├─ 每个测试单一职责\n├─ 使用Mock隔离依赖\n├─ 测试命名清晰（Given-When-Then）\n└─ 保持测试快速（<100ms）\n```\n\n### 第2层：集成测试层\n\n```text\n职责：\n├─ 测试范围：接口、服务间交互\n├─ 执行速度：秒级\n├─ 维护成本：中\n└─ 覆盖目标：业务流程\n\n技术选型：\n├─ API测试：Postman/Newman/REST Assured\n├─ 数据库测试：TestContainers\n├─ 消息队列测试：Embedded Kafka\n└─ 服务虚拟化：WireMock/Mountebank\n\n最佳实践：\n├─ 使用真实依赖（TestContainers）\n├─ 测试数据可构造、可清理\n├─ 验证接口契约\n├─ 覆盖正常/异常/边界场景\n└─ 保持测试独立性\n```\n\n### 第3层：E2E测试层\n\n```text\n职责：\n├─ 测试范围：完整用户流程\n├─ 执行速度：分钟级\n├─ 维护成本：高\n└─ 覆盖目标：核心路径\n\n技术选型：\n├─ Web UI：Playwright/Cypress/Selenium\n├─ 移动端：Appium/XCUITest/Espresso\n├─ 桌面端：Electron Test/WinAppDriver\n└─ 性能：JMeter/Locust/k6\n\n最佳实践：\n├─ 只覆盖核心路径（20%）\n├─ 使用Page Object模式\n├─ 数据驱动测试\n├─ 稳定的等待策略\n└─ 失败时自动截图/录屏\n```\n\n## 框架设计模式\n\n### Page Object Model\n\n```text\n优点：\n├─ 封装页面元素和操作\n├─ 减少代码重复\n├─ 易于维护\n└─ 可读性强\n\n示例结构：\ntests/\n├── pages/\n│ ├── login_page.py\n│ ├── home_page.py\n│ └── cart_page.py\n├── tests/\n│ ├── test_login.py\n│ ├── test_home.py\n│ └── test_cart.py\n├── fixtures/\n│ ├── test_data.py\n│ └── setup_teardown.py\n└── utils/\n ├── driver_factory.py\n └── report_generator.py\n```\n\n### 关键字驱动\n\n```text\n优点：\n├─ 业务人员可参与\n├─ 测试用例可读性强\n├─ 与实现分离\n└─ 易于复用\n\n示例：\n| 关键字 | 参数1 | 参数2 | 参数3 |\n|--------|-------|-------|-------|\n| 打开浏览器 | Chrome | | |\n| 输入用户名 | testuser | | |\n| 输入密码 | Test@123 | | |\n| 点击登录 | | | |\n| 验证跳转 | /home | | |\n```\n\n### 数据驱动\n\n```text\n优点：\n├─ 测试数据与逻辑分离\n├─ 易于添加新用例\n├─ 覆盖多种场景\n└─ 便于维护\n\n示例：\n@pytest.mark.parametrize(\"username,password,expected\", [\n (\"user1\", \"pass1\", \"success\"),\n (\"user2\", \"pass2\", \"success\"),\n (\"\", \"pass3\", \"error\"),\n (\"user4\", \"\", \"error\"),\n])\ndef test_login(username, password, expected):\n result = login(username, password)\n assert result == expected\n```\n\n## 框架选型决策\n\n| 维度 | Playwright | Cypress | Selenium |\n|------|-----------|---------|----------|\n| 浏览器支持 | 多浏览器 | 仅Chrome | 多语言 |\n| 执行速度 | 快 | 快 | 中等 |\n| 调试体验 | 好 | 优秀 | 一般 |\n| 学习曲线 | 中等 | 低 | 高 |\n| 社区生态 | 成长中 | 成熟 | 成熟 |\n| 适用场景 | 现代Web | 单页应用 | 传统Web |\n\n## 输出示例\n\n**设计Web UI自动化框架（团队5人，JS技术栈，1000+用例）**\n→ 分层：单元测试（Jest）→集成测试（Supertest）→E2E（Playwright）\n→ 模式：Page Object Model组织页面对象，关键字驱动封装业务操作\n→ 数据驱动：JSON/CSV管理测试数据，和环境配置分离\n→ CI/CD集成：GitHub Actions触发，Allure报告\n\n**API自动化框架设计**\n→ 分层：请求封装层→业务接口层→用例层→数据层\n\n## 检查清单\n\n架构设计完成后检查：\n- [ ] 分层是否清晰（单元/集成/E2E）？\n- [ ] 各层职责是否明确？\n- [ ] 框架选型是否合理？\n- [ ] 设计模式是否适用？\n- [ ] 可维护性是否考虑？\n- [ ] CI/CD集成是否规划？\n\nFile v1.7.7:_meta.json\n\n{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-test-automation-arch\",\n \"version\": \"1.7.7\",\n \"publishedAt\": 1790520149624\n}\n\nFile v1.7.7:skill-card.md\n\n## Description:\n\nGuides the design and refactoring of maintainable test automation architectures, including framework selection, test layers, data management, and CI integration.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nQA engineers and developers use this skill to design or refactor test automation frameworks, selecting appropriate test layers, patterns, tools, and maintenance and CI strategies before writing tests.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Examples or prompts may contain customer, payment, identity, or production data.\n\nMitigation: Use masked or synthetic test data and avoid pasting real sensitive information into prompts.\n\nRisk: Chinese-language guidance may be difficult for teams that need another language.\n\nMitigation: Request the preferred response language and review the design with the team before implementation.\n\n## Reference(s):\n\n- [ClawHub skill release](https://clawhub.ai/kokxi/skills/qa-test-automation-arch)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Markdown]\n\n**Output Format:** [Markdown architecture design with framework recommendations, layered test plan, and optional test-case table]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Architecture ID (ARCH-XXXX); coverage scope and gaps; maintenance and CI integration guidance. Responses may be in Chinese.]\n\n## Skill Version(s):\n\n1.7.7 (source: SKILL.md frontmatter and server-resolved release)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.7.6: 3 files, 5604 bytes\n\nFiles: skill-card.md (2239b), SKILL.md (8881b), _meta.json (142b)\n\nFile v1.7.6:SKILL.md\n\n---\r\nname: qa-test-automation-arch\r\nslug: qa-test-automation-arch\r\ndisplayName: 测试自动化架构\r\nversion: 1.7.5\r\ndescription: >-\r\n 当需要设计自动化测试框架、或者现有框架维护成本太高需要重构时使用此技能。运用 PageObject、分层测试、关键字驱动、数据驱动等模式设计可维护可扩展的自动化架构。不要直接写测试代码——先设计架构：选型（UI/API/单元）、分层（测试层/业务层/基础设施层）、数据管理（测试数据与脚本分离）和 CI 集成方案。好的自动化架构应该让写用例的人不需要懂底层实现。\r\n 本技能属于 QA Test Skills 技能集（49 个技能之一），完整工作流体验需安装全套：npx skills add Kokxi/qa-test-skills\r\n\r\nwhen_to_use: 用户说\"自动化架构\"、\"框架设计\"、\"自动化策略\"、\"自动化框架\"、\"测试框架架构\"、需要设计测试自动化架构、自动化维护困难需要重构时\r\nallowed-tools: Read Grep Glob Bash\r\nrelated_skills:\r\n upstream:\r\n - qa-tech-selection # 输入：技术选型结果\r\n - qa-test-strategy-design # 输入：测试策略\r\n downstream:\r\n - qa-ci-cd-testing # 输出：架构设计用于CI/CD集成\r\n - qa-api-testing # 输出：架构设计指导API测试\r\n - qa-mobile-testing\r\n - qa-tech-debt-management\r\ninput_format:\r\n required:\r\n - name: 测试策略\r\n type: object\r\n description: 来自qa-test-strategy-design的测试策略\r\n - name: 技术选型\r\n type: object\r\n description: 来自qa-tech-selection的技术选型建议\r\n optional:\r\n - name: 项目约束\r\n type: string\r\n description: 技术栈和团队限制\r\noutput_format:\r\n traceability:\r\n - 每份架构设计带唯一ID（ARCH-XXXX）\r\n structure:\r\n - 测试用例表格：固定 9 列（用例编号|测试类型|功能模块|测试标题|用例级别|预置条件|测试步骤|预期结果|风险等级）\r\n - 用例级别：P0≤20%（核心流程）/ P1≤40%（主要功能）/ P2≤30%（次要功能）/ P3≤10%（边缘场景）\r\n - 覆盖率：标注口径（基于现有需求/输入文档），禁止\"全覆盖/100%\"绝对化表述；缺失模块标注\"未覆盖+原因\"\r\n - automation_architecture: 自动化测试架构设计\r\n - framework_selection: 框架选择建议\r\n - layer_design: 分层设计\r\n - maintenance_strategy: 维护策略\r\ncategories: ['Development','Testing','DevOps']\r\ndepth_requirement_quantification:\r\n reference_value: \"根据架构复杂度调整设计深度：简单×1/中等×2/复杂×3\"\r\n minimum: \"至少覆盖层架构、工具集成、维护策略3个核心要素\"\r\nerror_recovery_guidance:\r\n on_failure: \"自动化架构遗漏维护策略时回退到技术选型补充\"\r\n retry_behavior: \"补充选型后重新设计架构\"\r\n---\r\n> ⚠️ 本技能单独使用效果有限，建议配合完整技能集（12 步工作流）使用。安装：npx skills add Kokxi/qa-test-skills\r\n\r\n> **⚠️ 安全警告**：本技能的示例可能涉及订单号、支付金额、截图、身份证、手机号等敏感数据。\r\n> 实际使用时请勿粘贴真实生产数据、客户信息或财务凭证；测试前应脱敏/掩码处理。\r\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\r\n\r\n# 测试自动化架构设计\r\n\r\n## 核心原则\r\n\r\n好的自动化架构——分层清晰、职责单一、易于维护、快速反馈。\r\n\r\n## 测试自动化金字塔\r\n\r\n> 📌 本节与 qa-test-strategy-design「测试金字塔」概念对应，但分层名称和比例不同——本技能侧重自动化落地（集成测试层名、70/20/10 比例），strategy-design 侧重策略规划（接口测试层名、60/30/10 比例）。修改时请确认两处含义，避免矛盾。\r\n\r\n```text\r\n ┌─────────────┐\r\n │ E2E测试 │ 10%\r\n │ (UI/API) │\r\n ├─────────────┤\r\n │ 集成测试 │ 20%\r\n │ (接口/服务) │\r\n ├─────────────┤\r\n │ 单元测试 │ 70%\r\n │ (函数/类) │\r\n └─────────────┘\r\n```\r\n\r\n## 分层架构设计\r\n\r\n### 第1层：单元测试层\r\n\r\n```text\r\n职责：\r\n├─ 测试范围：函数、类、模块\r\n├─ 执行速度：毫秒级\r\n├─ 维护成本：低\r\n└─ 覆盖目标：核心逻辑\r\n\r\n技术选型：\r\n├─ Java：JUnit 5 + Mockito\r\n├─ Python：Pytest + Mock\r\n├─ JavaScript：Jest + Sinon\r\n└─ Go：testing + testify\r\n\r\n最佳实践：\r\n├─ 测试与代码同步维护\r\n├─ 每个测试单一职责\r\n├─ 使用Mock隔离依赖\r\n├─ 测试命名清晰（Given-When-Then）\r\n└─ 保持测试快速（<100ms）\r\n```\r\n\r\n### 第2层：集成测试层\r\n\r\n```text\r\n职责：\r\n├─ 测试范围：接口、服务间交互\r\n├─ 执行速度：秒级\r\n├─ 维护成本：中\r\n└─ 覆盖目标：业务流程\r\n\r\n技术选型：\r\n├─ API测试：Postman/Newman/REST Assured\r\n├─ 数据库测试：TestContainers\r\n├─ 消息队列测试：Embedded Kafka\r\n└─ 服务虚拟化：WireMock/Mountebank\r\n\r\n最佳实践：\r\n├─ 使用真实依赖（TestContainers）\r\n├─ 测试数据可构造、可清理\r\n├─ 验证接口契约\r\n├─ 覆盖正常/异常/边界场景\r\n└─ 保持测试独立性\r\n```\r\n\r\n### 第3层：E2E测试层\r\n\r\n```text\r\n职责：\r\n├─ 测试范围：完整用户流程\r\n├─ 执行速度：分钟级\r\n├─ 维护成本：高\r\n└─ 覆盖目标：核心路径\r\n\r\n技术选型：\r\n├─ Web UI：Playwright/Cypress/Selenium\r\n├─ 移动端：Appium/XCUITest/Espresso\r\n├─ 桌面端：Electron Test/WinAppDriver\r\n└─ 性能：JMeter/Locust/k6\r\n\r\n最佳实践：\r\n├─ 只覆盖核心路径（20%）\r\n├─ 使用Page Object模式\r\n├─ 数据驱动测试\r\n├─ 稳定的等待策略\r\n└─ 失败时自动截图/录屏\r\n```\r\n\r\n## 框架设计模式\r\n\r\n### Page Object Model\r\n\r\n```text\r\n优点：\r\n├─ 封装页面元素和操作\r\n├─ 减少代码重复\r\n├─ 易于维护\r\n└─ 可读性强\r\n\r\n示例结构：\r\ntests/\r\n├── pages/\r\n│ ├── login_page.py\r\n│ ├── home_page.py\r\n│ └── cart_page.py\r\n├── tests/\r\n│ ├── test_login.py\r\n│ ├── test_home.py\r\n│ └── test_cart.py\r\n├── fixtures/\r\n│ ├── test_data.py\r\n│ └── setup_teardown.py\r\n└── utils/\r\n ├── driver_factory.py\r\n └── report_generator.py\r\n```\r\n\r\n### 关键字驱动\r\n\r\n```text\r\n优点：\r\n├─ 业务人员可参与\r\n├─ 测试用例可读性强\r\n├─ 与实现分离\r\n└─ 易于复用\r\n\r\n示例：\r\n| 关键字 | 参数1 | 参数2 | 参数3 |\r\n|--------|-------|-------|-------|\r\n| 打开浏览器 | Chrome | | |\r\n| 输入用户名 | testuser | | |\r\n| 输入密码 | Test@123 | | |\r\n| 点击登录 | | | |\r\n| 验证跳转 | /home | | |\r\n```\r\n\r\n### 数据驱动\r\n\r\n```text\r\n优点：\r\n├─ 测试数据与逻辑分离\r\n├─ 易于添加新用例\r\n├─ 覆盖多种场景\r\n└─ 便于维护\r\n\r\n示例：\r\n@pytest.mark.parametrize(\"username,password,expected\", [\r\n (\"user1\", \"pass1\", \"success\"),\r\n (\"user2\", \"pass2\", \"success\"),\r\n (\"\", \"pass3\", \"error\"),\r\n (\"user4\", \"\", \"error\"),\r\n])\r\ndef test_login(username, password, expected):\r\n result = login(username, password)\r\n assert result == expected\r\n```\r\n\r\n## 框架选型决策\r\n\r\n| 维度 | Playwright | Cypress | Selenium |\r\n|------|-----------|---------|----------|\r\n| 浏览器支持 | 多浏览器 | 仅Chrome | 多语言 |\r\n| 执行速度 | 快 | 快 | 中等 |\r\n| 调试体验 | 好 | 优秀 | 一般 |\r\n| 学习曲线 | 中等 | 低 | 高 |\r\n| 社区生态 | 成长中 | 成熟 | 成熟 |\r\n| 适用场景 | 现代Web | 单页应用 | 传统Web |\r\n\r\n## 输出示例\r\n\r\n**设计Web UI自动化框架（团队5人，JS技术栈，1000+用例）**\r\n→ 分层：单元测试（Jest）→集成测试（Supertest）→E2E（Playwright）\r\n→ 模式：Page Object Model组织页面对象，关键字驱动封装业务操作\r\n→ 数据驱动：JSON/CSV管理测试数据，和环境配置分离\r\n→ CI/CD集成：GitHub Actions触发，Allure报告\r\n\r\n**API自动化框架设计**\r\n→ 分层：请求封装层→业务接口层→用例层→数据层\r\n\r\n## 检查清单\r\n\r\n架构设计完成后检查：\r\n- [ ] 分层是否清晰（单元/集成/E2E）？\r\n- [ ] 各层职责是否明确？\r\n- [ ] 框架选型是否合理？\r\n- [ ] 设计模式是否适用？\r\n- [ ] 可维护性是否考虑？\r\n- [ ] CI/CD集成是否规划？\n\nFile v1.7.6:_meta.json\n\n{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-test-automation-arch\",\n \"version\": \"1.7.6\",\n \"publishedAt\": 1788266859368\n}\n\nFile v1.7.6:skill-card.md\n\n## Description:\n\nHelps QA engineers design maintainable automated test automation frameworks using Page Object, layered testing, keyword-driven testing, data-driven testing, data separation, and CI integration.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nQA engineers, developers, and test automation architects use this skill when planning a new automation framework or refactoring one that has become costly to maintain. It focuses on architecture choices for UI, API, and unit testing layers, test data separation, maintenance strategy, and CI integration rather than writing individual test code first.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill recommends installing a larger unpinned external skill collection.\n\nMitigation: Review and pin the referenced `Kokxi/qa-test-skills` source before running the suggested `npx` install command, preferably in an isolated environment without sensitive credentials.\n\nRisk: QA workflow inputs may include real customer, production, identity, payment, or financial data.\n\nMitigation: Use synthetic, masked, or otherwise sanitized data and avoid pasting sensitive production information into the skill.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/kokxi/skills/qa-test-automation-arch)\n\n## Skill Output:\n\n**Output Type(s):** [markdown, code, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown with tables, architecture outlines, code examples, shell commands, and configuration guidance]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Architecture outputs should include an ARCH-XXXX identifier, testing-layer design, framework selection, maintenance strategy, and CI integration guidance when applicable.]\n\n## Skill Version(s):\n\n1.7.6 (source: server release metadata; artifact frontmatter lists 1.7.5)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.7.5: 3 files, 5386 bytes\n\nFiles: skill-card.md (2095b), SKILL.md (8337b), _meta.json (142b)\n\nFile v1.7.5:SKILL.md\n\n---\nname: qa-test-automation-arch\nslug: qa-test-automation-arch\ndisplayName: Test Automation Arch\nversion: 1.7.5\ndescription: >-\n 当需要设计自动化测试框架、或者现有框架维护成本太高需要重构时使用此技能。运用 PageObject、分层测试、关键字驱动、数据驱动等模式设计可维护可扩展的自动化架构。不要直接写测试代码——先设计架构：选型（UI/API/单元）、分层（测试层/业务层/基础设施层）、数据管理（测试数据与脚本分离）和 CI 集成方案。好的自动化架构应该让写用例的人不需要懂底层实现。\n\nwhen_to_use: 用户说\"自动化架构\"、\"框架设计\"、\"自动化策略\"、\"自动化框架\"、\"测试框架架构\"、需要设计测试自动化架构、自动化维护困难需要重构时\nallowed-tools: Read Grep Glob Bash\nrelated_skills:\n upstream:\n - qa-tech-selection # 输入：技术选型结果\n - qa-test-strategy-design # 输入：测试策略\n downstream:\n - qa-ci-cd-testing # 输出：架构设计用于CI/CD集成\n - qa-api-testing # 输出：架构设计指导API测试\n - qa-mobile-testing\n - qa-tech-debt-management\ninput_format:\n required:\n - name: 测试策略\n type: object\n description: 来自qa-test-strategy-design的测试策略\n - name: 技术选型\n type: object\n description: 来自qa-tech-selection的技术选型建议\n optional:\n - name: 项目约束\n type: string\n description: 技术栈和团队限制\noutput_format:\n traceability:\n - 每份架构设计带唯一ID（ARCH-XXXX）\n structure:\n - 测试用例表格：固定 9 列（用例编号|测试类型|功能模块|测试标题|用例级别|预置条件|测试步骤|预期结果|风险等级）\n - 用例级别：P0≤20%（核心流程）/ P1≤40%（主要功能）/ P2≤30%（次要功能）/ P3≤10%（边缘场景）\n - 覆盖率：标注口径（基于现有需求/输入文档），禁止\"全覆盖/100%\"绝对化表述；缺失模块标注\"未覆盖+原因\"\n - automation_architecture: 自动化测试架构设计\n - framework_selection: 框架选择建议\n - layer_design: 分层设计\n - maintenance_strategy: 维护策略\ncategories: ['Development','Testing','DevOps']\ndepth_requirement_quantification:\n reference_value: \"根据架构复杂度调整设计深度：简单×1/中等×2/复杂×3\"\n minimum: \"至少覆盖层架构、工具集成、维护策略3个核心要素\"\nerror_recovery_guidance:\n on_failure: \"自动化架构遗漏维护策略时回退到技术选型补充\"\n retry_behavior: \"补充选型后重新设计架构\"\n---\n> **⚠️ 安全警告**：本技能的示例可能涉及订单号、支付金额、截图、身份证、手机号等敏感数据。\n> 实际使用时请勿粘贴真实生产数据、客户信息或财务凭证；测试前应脱敏/掩码处理。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 测试自动化架构设计\n\n## 核心原则\n\n好的自动化架构——分层清晰、职责单一、易于维护、快速反馈。\n\n## 测试自动化金字塔\n\n> 📌 本节与 qa-test-strategy-design「测试金字塔」概念对应，但分层名称和比例不同——本技能侧重自动化落地（集成测试层名、70/20/10 比例），strategy-design 侧重策略规划（接口测试层名、60/30/10 比例）。修改时请确认两处含义，避免矛盾。\n\n```text\n ┌─────────────┐\n │ E2E测试 │ 10%\n │ (UI/API) │\n ├─────────────┤\n │ 集成测试 │ 20%\n │ (接口/服务) │\n ├─────────────┤\n │ 单元测试 │ 70%\n │ (函数/类) │\n └─────────────┘\n```\n\n## 分层架构设计\n\n### 第1层：单元测试层\n\n```text\n职责：\n├─ 测试范围：函数、类、模块\n├─ 执行速度：毫秒级\n├─ 维护成本：低\n└─ 覆盖目标：核心逻辑\n\n技术选型：\n├─ Java：JUnit 5 + Mockito\n├─ Python：Pytest + Mock\n├─ JavaScript：Jest + Sinon\n└─ Go：testing + testify\n\n最佳实践：\n├─ 测试与代码同步维护\n├─ 每个测试单一职责\n├─ 使用Mock隔离依赖\n├─ 测试命名清晰（Given-When-Then）\n└─ 保持测试快速（<100ms）\n```\n\n### 第2层：集成测试层\n\n```text\n职责：\n├─ 测试范围：接口、服务间交互\n├─ 执行速度：秒级\n├─ 维护成本：中\n└─ 覆盖目标：业务流程\n\n技术选型：\n├─ API测试：Postman/Newman/REST Assured\n├─ 数据库测试：TestContainers\n├─ 消息队列测试：Embedded Kafka\n└─ 服务虚拟化：WireMock/Mountebank\n\n最佳实践：\n├─ 使用真实依赖（TestContainers）\n├─ 测试数据可构造、可清理\n├─ 验证接口契约\n├─ 覆盖正常/异常/边界场景\n└─ 保持测试独立性\n```\n\n### 第3层：E2E测试层\n\n```text\n职责：\n├─ 测试范围：完整用户流程\n├─ 执行速度：分钟级\n├─ 维护成本：高\n└─ 覆盖目标：核心路径\n\n技术选型：\n├─ Web UI：Playwright/Cypress/Selenium\n├─ 移动端：Appium/XCUITest/Espresso\n├─ 桌面端：Electron Test/WinAppDriver\n└─ 性能：JMeter/Locust/k6\n\n最佳实践：\n├─ 只覆盖核心路径（20%）\n├─ 使用Page Object模式\n├─ 数据驱动测试\n├─ 稳定的等待策略\n└─ 失败时自动截图/录屏\n```\n\n## 框架设计模式\n\n### Page Object Model\n\n```text\n优点：\n├─ 封装页面元素和操作\n├─ 减少代码重复\n├─ 易于维护\n└─ 可读性强\n\n示例结构：\ntests/\n├── pages/\n│ ├── login_page.py\n│ ├── home_page.py\n│ └── cart_page.py\n├── tests/\n│ ├── test_login.py\n│ ├── test_home.py\n│ └── test_cart.py\n├── fixtures/\n│ ├── test_data.py\n│ └── setup_teardown.py\n└── utils/\n ├── driver_factory.py\n └── report_generator.py\n```\n\n### 关键字驱动\n\n```text\n优点：\n├─ 业务人员可参与\n├─ 测试用例可读性强\n├─ 与实现分离\n└─ 易于复用\n\n示例：\n| 关键字 | 参数1 | 参数2 | 参数3 |\n|--------|-------|-------|-------|\n| 打开浏览器 | Chrome | | |\n| 输入用户名 | testuser | | |\n| 输入密码 | Test@123 | | |\n| 点击登录 | | | |\n| 验证跳转 | /home | | |\n```\n\n### 数据驱动\n\n```text\n优点：\n├─ 测试数据与逻辑分离\n├─ 易于添加新用例\n├─ 覆盖多种场景\n└─ 便于维护\n\n示例：\n@pytest.mark.parametrize(\"username,password,expected\", [\n (\"user1\", \"pass1\", \"success\"),\n (\"user2\", \"pass2\", \"success\"),\n (\"\", \"pass3\", \"error\"),\n (\"user4\", \"\", \"error\"),\n])\ndef test_login(username, password, expected):\n result = login(username, password)\n assert result == expected\n```\n\n## 框架选型决策\n\n| 维度 | Playwright | Cypress | Selenium |\n|------|-----------|---------|----------|\n| 浏览器支持 | 多浏览器 | 仅Chrome | 多语言 |\n| 执行速度 | 快 | 快 | 中等 |\n| 调试体验 | 好 | 优秀 | 一般 |\n| 学习曲线 | 中等 | 低 | 高 |\n| 社区生态 | 成长中 | 成熟 | 成熟 |\n| 适用场景 | 现代Web | 单页应用 | 传统Web |\n\n## 输出示例\n\n**设计Web UI自动化框架（团队5人，JS技术栈，1000+用例）**\n→ 分层：单元测试（Jest）→集成测试（Supertest）→E2E（Playwright）\n→ 模式：Page Object Model组织页面对象，关键字驱动封装业务操作\n→ 数据驱动：JSON/CSV管理测试数据，和环境配置分离\n→ CI/CD集成：GitHub Actions触发，Allure报告\n\n**API自动化框架设计**\n→ 分层：请求封装层→业务接口层→用例层→数据层\n\n## 检查清单\n\n架构设计完成后检查：\n- [ ] 分层是否清晰（单元/集成/E2E）？\n- [ ] 各层职责是否明确？\n- [ ] 框架选型是否合理？\n- [ ] 设计模式是否适用？\n- [ ] 可维护性是否考虑？\n- [ ] CI/CD集成是否规划？\n\nFile v1.7.5:_meta.json\n\n{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-test-automation-arch\",\n \"version\": \"1.7.5\",\n \"publishedAt\": 1788103224487\n}\n\nFile v1.7.5:skill-card.md\n\n## Description:\n\nHelps agents design maintainable test automation architecture using Page Object, layered testing, keyword-driven testing, data-driven testing, framework selection, data management, and CI integration guidance.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, QA engineers, and automation architects use this skill to plan test automation frameworks before implementation. It is intended for architecture decisions across unit, integration, E2E, API, UI, mobile, data management, maintainability, and CI/CD integration.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: QA examples or project inputs may contain order numbers, payment details, screenshots, IDs, phone numbers, or other sensitive data.\n\nMitigation: Mask or remove sensitive production, customer, and financial data before using the skill.\n\nRisk: The skill may propose shell commands or project file changes while analyzing an automation architecture.\n\nMitigation: Review proposed commands and changes before execution, especially in shared or production-adjacent workspaces.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/kokxi/skills/qa-test-automation-arch)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown architecture guidance with tables, structured recommendations, code examples, and command suggestions when needed.]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Outputs should include traceable architecture IDs, avoid absolute coverage claims, and separate test data from test logic.]\n\n## Skill Version(s):\n\n1.7.5 (source: frontmatter and release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.7.0: 3 files, 5075 bytes\n\nFiles: skill-card.md (2012b), SKILL.md (7896b), _meta.json (142b)\n\nFile v1.7.0:SKILL.md\n\n---\nname: qa-test-automation-arch\nslug: qa-test-automation-arch\ndisplayName: Test Automation Arch\nversion: 1.7.0\ndescription: >-\n 当需要设计自动化测试框架、或者现有框架维护成本太高需要重构时使用此技能。运用 PageObject、分层测试、关键字驱动、数据驱动等模式设计可维护可扩展的自动化架构。不要直接写测试代码——先设计架构：选型（UI/API/单元）、分层（测试层/业务层/基础设施层）、数据管理（测试数据与脚本分离）和 CI 集成方案。好的自动化架构应该让写用例的人不需要懂底层实现。\n\nwhen_to_use: 用户说\"自动化架构\"、\"框架设计\"、\"自动化策略\"、\"自动化框架\"、\"测试框架架构\"、需要设计测试自动化架构、自动化维护困难需要重构时\nallowed-tools: Read Grep Glob Bash\nrelated_skills:\n upstream:\n - qa-tech-selection # 输入：技术选型结果\n - qa-test-strategy-design # 输入：测试策略\n downstream:\n - qa-ci-cd-testing # 输出：架构设计用于CI/CD集成\n - qa-api-testing # 输出：架构设计指导API测试\n - qa-mobile-testing\n - qa-tech-debt-management\ninput_format:\n required:\n - name: 测试策略\n type: object\n description: 来自qa-test-strategy-design的测试策略\n - name: 技术选型\n type: object\n description: 来自qa-tech-selection的技术选型建议\n optional:\n - name: 项目约束\n type: string\n description: 技术栈和团队限制\noutput_format:\n traceability:\n - 每份架构设计带唯一ID（ARCH-XXXX）\n structure:\n - automation_architecture: 自动化测试架构设计\n - framework_selection: 框架选择建议\n - layer_design: 分层设计\n - maintenance_strategy: 维护策略\ncategories: ['Development','Testing','DevOps']\ndepth_requirement_quantification:\n reference_value: \"根据架构复杂度调整设计深度：简单×1/中等×2/复杂×3\"\n minimum: \"至少覆盖层架构、工具集成、维护策略3个核心要素\"\nerror_recovery_guidance:\n on_failure: \"自动化架构遗漏维护策略时回退到技术选型补充\"\n retry_behavior: \"补充选型后重新设计架构\"\n---\n> **⚠️ 安全警告**：本技能的示例可能涉及订单号、支付金额、截图、身份证、手机号等敏感数据。\n> 实际使用时请勿粘贴真实生产数据、客户信息或财务凭证；测试前应脱敏/掩码处理。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 测试自动化架构设计\n\n## 核心原则\n\n好的自动化架构——分层清晰、职责单一、易于维护、快速反馈。\n\n## 测试自动化金字塔\n\n> 📌 本节与 qa-test-strategy-design「测试金字塔」概念对应，但分层名称和比例不同——本技能侧重自动化落地（集成测试层名、70/20/10 比例），strategy-design 侧重策略规划（接口测试层名、60/30/10 比例）。修改时请确认两处含义，避免矛盾。\n\n```text\n ┌─────────────┐\n │ E2E测试 │ 10%\n │ (UI/API) │\n ├─────────────┤\n │ 集成测试 │ 20%\n │ (接口/服务) │\n ├─────────────┤\n │ 单元测试 │ 70%\n │ (函数/类) │\n └─────────────┘\n```\n\n## 分层架构设计\n\n### 第1层：单元测试层\n\n```text\n职责：\n├─ 测试范围：函数、类、模块\n├─ 执行速度：毫秒级\n├─ 维护成本：低\n└─ 覆盖目标：核心逻辑\n\n技术选型：\n├─ Java：JUnit 5 + Mockito\n├─ Python：Pytest + Mock\n├─ JavaScript：Jest + Sinon\n└─ Go：testing + testify\n\n最佳实践：\n├─ 测试与代码同步维护\n├─ 每个测试单一职责\n├─ 使用Mock隔离依赖\n├─ 测试命名清晰（Given-When-Then）\n└─ 保持测试快速（<100ms）\n```\n\n### 第2层：集成测试层\n\n```text\n职责：\n├─ 测试范围：接口、服务间交互\n├─ 执行速度：秒级\n├─ 维护成本：中\n└─ 覆盖目标：业务流程\n\n技术选型：\n├─ API测试：Postman/Newman/REST Assured\n├─ 数据库测试：TestContainers\n├─ 消息队列测试：Embedded Kafka\n└─ 服务虚拟化：WireMock/Mountebank\n\n最佳实践：\n├─ 使用真实依赖（TestContainers）\n├─ 测试数据可构造、可清理\n├─ 验证接口契约\n├─ 覆盖正常/异常/边界场景\n└─ 保持测试独立性\n```\n\n### 第3层：E2E测试层\n\n```text\n职责：\n├─ 测试范围：完整用户流程\n├─ 执行速度：分钟级\n├─ 维护成本：高\n└─ 覆盖目标：核心路径\n\n技术选型：\n├─ Web UI：Playwright/Cypress/Selenium\n├─ 移动端：Appium/XCUITest/Espresso\n├─ 桌面端：Electron Test/WinAppDriver\n└─ 性能：JMeter/Locust/k6\n\n最佳实践：\n├─ 只覆盖核心路径（20%）\n├─ 使用Page Object模式\n├─ 数据驱动测试\n├─ 稳定的等待策略\n└─ 失败时自动截图/录屏\n```\n\n## 框架设计模式\n\n### Page Object Model\n\n```text\n优点：\n├─ 封装页面元素和操作\n├─ 减少代码重复\n├─ 易于维护\n└─ 可读性强\n\n示例结构：\ntests/\n├── pages/\n│ ├── login_page.py\n│ ├── home_page.py\n│ └── cart_page.py\n├── tests/\n│ ├── test_login.py\n│ ├── test_home.py\n│ └── test_cart.py\n├── fixtures/\n│ ├── test_data.py\n│ └── setup_teardown.py\n└── utils/\n ├── driver_factory.py\n └── report_generator.py\n```\n\n### 关键字驱动\n\n```text\n优点：\n├─ 业务人员可参与\n├─ 测试用例可读性强\n├─ 与实现分离\n└─ 易于复用\n\n示例：\n| 关键字 | 参数1 | 参数2 | 参数3 |\n|--------|-------|-------|-------|\n| 打开浏览器 | Chrome | | |\n| 输入用户名 | testuser | | |\n| 输入密码 | Test@123 | | |\n| 点击登录 | | | |\n| 验证跳转 | /home | | |\n```\n\n### 数据驱动\n\n```text\n优点：\n├─ 测试数据与逻辑分离\n├─ 易于添加新用例\n├─ 覆盖多种场景\n└─ 便于维护\n\n示例：\n@pytest.mark.parametrize(\"username,password,expected\", [\n (\"user1\", \"pass1\", \"success\"),\n (\"user2\", \"pass2\", \"success\"),\n (\"\", \"pass3\", \"error\"),\n (\"user4\", \"\", \"error\"),\n])\ndef test_login(username, password, expected):\n result = login(username, password)\n assert result == expected\n```\n\n## 框架选型决策\n\n| 维度 | Playwright | Cypress | Selenium |\n|------|-----------|---------|----------|\n| 浏览器支持 | 多浏览器 | 仅Chrome | 多语言 |\n| 执行速度 | 快 | 快 | 中等 |\n| 调试体验 | 好 | 优秀 | 一般 |\n| 学习曲线 | 中等 | 低 | 高 |\n| 社区生态 | 成长中 | 成熟 | 成熟 |\n| 适用场景 | 现代Web | 单页应用 | 传统Web |\n\n## 输出示例\n\n**设计Web UI自动化框架（团队5人，JS技术栈，1000+用例）**\n→ 分层：单元测试（Jest）→集成测试（Supertest）→E2E（Playwright）\n→ 模式：Page Object Model组织页面对象，关键字驱动封装业务操作\n→ 数据驱动：JSON/CSV管理测试数据，和环境配置分离\n→ CI/CD集成：GitHub Actions触发，Allure报告\n\n**API自动化框架设计**\n→ 分层：请求封装层→业务接口层→用例层→数据层\n\n## 检查清单\n\n架构设计完成后检查：\n- [ ] 分层是否清晰（单元/集成/E2E）？\n- [ ] 各层职责是否明确？\n- [ ] 框架选型是否合理？\n- [ ] 设计模式是否适用？\n- [ ] 可维护性是否考虑？\n- [ ] CI/CD集成是否规划？\n\nFile v1.7.0:_meta.json\n\n{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-test-automation-arch\",\n \"version\": \"1.7.0\",\n \"publishedAt\": 1786890793608\n}\n\nFile v1.7.0:skill-card.md\n\n## Description:\n\nDesigns maintainable test automation architectures using Page Object, layered testing, keyword-driven, and data-driven patterns, with framework selection, data management, and CI integration guidance.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, QA engineers, and test automation architects use this skill to plan or refactor automation frameworks before writing test code. It helps select UI, API, and unit testing layers, separate test data from scripts, and define maintainability and CI integration practices.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Automation architecture prompts may include real customer, payment, identity, production, or financial data.\n\nMitigation: Use sanitized or masked test data and avoid pasting real sensitive or production data into prompts.\n\nRisk: Broad framework or automation requests may invoke the skill even when implementation code or operational changes are expected.\n\nMitigation: Confirm the task is architecture guidance and review recommendations before applying them to production workflows.\n\n## Reference(s):\n\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Markdown, Configuration]\n\n**Output Format:** [Structured Markdown guidance with architecture recommendations, framework selection, layer design, and maintenance strategy]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Architecture designs include traceability IDs and should cover layered architecture, tool integration, and maintenance strategy.]\n\n## Skill Version(s):\n\n1.7.0 (source: frontmatter and server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.6.3: 3 files, 5039 bytes\n\nFiles: skill-card.md (1930b), SKILL.md (7896b), _meta.json (142b)\n\nFile v1.6.3:SKILL.md\n\n---\nname: qa-test-automation-arch\nslug: qa-test-automation-arch\ndisplayName: Test Automation Arch\nversion: 1.6.3\ndescription: >-\n 当需要设计自动化测试框架、或者现有框架维护成本太高需要重构时使用此技能。运用 PageObject、分层测试、关键字驱动、数据驱动等模式设计可维护可扩展的自动化架构。不要直接写测试代码——先设计架构：选型（UI/API/单元）、分层（测试层/业务层/基础设施层）、数据管理（测试数据与脚本分离）和 CI 集成方案。好的自动化架构应该让写用例的人不需要懂底层实现。\n\nwhen_to_use: 用户说\"自动化架构\"、\"框架设计\"、\"自动化策略\"、\"自动化框架\"、\"测试框架架构\"、需要设计测试自动化架构、自动化维护困难需要重构时\nallowed-tools: Read Grep Glob Bash\nrelated_skills:\n upstream:\n - qa-tech-selection # 输入：技术选型结果\n - qa-test-strategy-design # 输入：测试策略\n downstream:\n - qa-ci-cd-testing # 输出：架构设计用于CI/CD集成\n - qa-api-testing # 输出：架构设计指导API测试\n - qa-mobile-testing\n - qa-tech-debt-management\ninput_format:\n required:\n - name: 测试策略\n type: object\n description: 来自qa-test-strategy-design的测试策略\n - name: 技术选型\n type: object\n description: 来自qa-tech-selection的技术选型建议\n optional:\n - name: 项目约束\n type: string\n description: 技术栈和团队限制\noutput_format:\n traceability:\n - 每份架构设计带唯一ID（ARCH-XXXX）\n structure:\n - automation_architecture: 自动化测试架构设计\n - framework_selection: 框架选择建议\n - layer_design: 分层设计\n - maintenance_strategy: 维护策略\ncategories: ['Development','Testing','DevOps']\ndepth_requirement_quantification:\n reference_value: \"根据架构复杂度调整设计深度：简单×1/中等×2/复杂×3\"\n minimum: \"至少覆盖层架构、工具集成、维护策略3个核心要素\"\nerror_recovery_guidance:\n on_failure: \"自动化架构遗漏维护策略时回退到技术选型补充\"\n retry_behavior: \"补充选型后重新设计架构\"\n---\n> **⚠️ 安全警告**：本技能的示例可能涉及订单号、支付金额、截图、身份证、手机号等敏感数据。\n> 实际使用时请勿粘贴真实生产数据、客户信息或财务凭证；测试前应脱敏/掩码处理。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 测试自动化架构设计\n\n## 核心原则\n\n好的自动化架构——分层清晰、职责单一、易于维护、快速反馈。\n\n## 测试自动化金字塔\n\n> 📌 本节与 qa-test-strategy-design「测试金字塔」概念对应，但分层名称和比例不同——本技能侧重自动化落地（集成测试层名、70/20/10 比例），strategy-design 侧重策略规划（接口测试层名、60/30/10 比例）。修改时请确认两处含义，避免矛盾。\n\n```text\n ┌─────────────┐\n │ E2E测试 │ 10%\n │ (UI/API) │\n ├─────────────┤\n │ 集成测试 │ 20%\n │ (接口/服务) │\n ├─────────────┤\n │ 单元测试 │ 70%\n │ (函数/类) │\n └─────────────┘\n```\n\n## 分层架构设计\n\n### 第1层：单元测试层\n\n```text\n职责：\n├─ 测试范围：函数、类、模块\n├─ 执行速度：毫秒级\n├─ 维护成本：低\n└─ 覆盖目标：核心逻辑\n\n技术选型：\n├─ Java：JUnit 5 + Mockito\n├─ Python：Pytest + Mock\n├─ JavaScript：Jest + Sinon\n└─ Go：testing + testify\n\n最佳实践：\n├─ 测试与代码同步维护\n├─ 每个测试单一职责\n├─ 使用Mock隔离依赖\n├─ 测试命名清晰（Given-When-Then）\n└─ 保持测试快速（<100ms）\n```\n\n### 第2层：集成测试层\n\n```text\n职责：\n├─ 测试范围：接口、服务间交互\n├─ 执行速度：秒级\n├─ 维护成本：中\n└─ 覆盖目标：业务流程\n\n技术选型：\n├─ API测试：Postman/Newman/REST Assured\n├─ 数据库测试：TestContainers\n├─ 消息队列测试：Embedded Kafka\n└─ 服务虚拟化：WireMock/Mountebank\n\n最佳实践：\n├─ 使用真实依赖（TestContainers）\n├─ 测试数据可构造、可清理\n├─ 验证接口契约\n├─ 覆盖正常/异常/边界场景\n└─ 保持测试独立性\n```\n\n### 第3层：E2E测试层\n\n```text\n职责：\n├─ 测试范围：完整用户流程\n├─ 执行速度：分钟级\n├─ 维护成本：高\n└─ 覆盖目标：核心路径\n\n技术选型：\n├─ Web UI：Playwright/Cypress/Selenium\n├─ 移动端：Appium/XCUITest/Espresso\n├─ 桌面端：Electron Test/WinAppDriver\n└─ 性能：JMeter/Locust/k6\n\n最佳实践：\n├─ 只覆盖核心路径（20%）\n├─ 使用Page Object模式\n├─ 数据驱动测试\n├─ 稳定的等待策略\n└─ 失败时自动截图/录屏\n```\n\n## 框架设计模式\n\n### Page Object Model\n\n```text\n优点：\n├─ 封装页面元素和操作\n├─ 减少代码重复\n├─ 易于维护\n└─ 可读性强\n\n示例结构：\ntests/\n├── pages/\n│ ├── login_page.py\n│ ├── home_page.py\n│ └── cart_page.py\n├── tests/\n│ ├── test_login.py\n│ ├── test_home.py\n│ └── test_cart.py\n├── fixtures/\n│ ├── test_data.py\n│ └── setup_teardown.py\n└── utils/\n ├── driver_factory.py\n └── report_generator.py\n```\n\n### 关键字驱动\n\n```text\n优点：\n├─ 业务人员可参与\n├─ 测试用例可读性强\n├─ 与实现分离\n└─ 易于复用\n\n示例：\n| 关键字 | 参数1 | 参数2 | 参数3 |\n|--------|-------|-------|-------|\n| 打开浏览器 | Chrome | | |\n| 输入用户名 | testuser | | |\n| 输入密码 | Test@123 | | |\n| 点击登录 | | | |\n| 验证跳转 | /home | | |\n```\n\n### 数据驱动\n\n```text\n优点：\n├─ 测试数据与逻辑分离\n├─ 易于添加新用例\n├─ 覆盖多种场景\n└─ 便于维护\n\n示例：\n@pytest.mark.parametrize(\"username,password,expected\", [\n (\"user1\", \"pass1\", \"success\"),\n (\"user2\", \"pass2\", \"success\"),\n (\"\", \"pass3\", \"error\"),\n (\"user4\", \"\", \"error\"),\n])\ndef test_login(username, password, expected):\n result = login(username, password)\n assert result == expected\n```\n\n## 框架选型决策\n\n| 维度 | Playwright | Cypress | Selenium |\n|------|-----------|---------|----------|\n| 浏览器支持 | 多浏览器 | 仅Chrome | 多语言 |\n| 执行速度 | 快 | 快 | 中等 |\n| 调试体验 | 好 | 优秀 | 一般 |\n| 学习曲线 | 中等 | 低 | 高 |\n| 社区生态 | 成长中 | 成熟 | 成熟 |\n| 适用场景 | 现代Web | 单页应用 | 传统Web |\n\n## 输出示例\n\n**设计Web UI自动化框架（团队5人，JS技术栈，1000+用例）**\n→ 分层：单元测试（Jest）→集成测试（Supertest）→E2E（Playwright）\n→ 模式：Page Object Model组织页面对象，关键字驱动封装业务操作\n→ 数据驱动：JSON/CSV管理测试数据，和环境配置分离\n→ CI/CD集成：GitHub Actions触发，Allure报告\n\n**API自动化框架设计**\n→ 分层：请求封装层→业务接口层→用例层→数据层\n\n## 检查清单\n\n架构设计完成后检查：\n- [ ] 分层是否清晰（单元/集成/E2E）？\n- [ ] 各层职责是否明确？\n- [ ] 框架选型是否合理？\n- [ ] 设计模式是否适用？\n- [ ] 可维护性是否考虑？\n- [ ] CI/CD集成是否规划？\n\nFile v1.6.3:_meta.json\n\n{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-test-automation-arch\",\n \"version\": \"1.6.3\",\n \"publishedAt\": 1786548562501\n}\n\nFile v1.6.3:skill-card.md\n\n## Description:\n\nUse this skill to design maintainable automated testing frameworks or refactor costly ones with Page Object, layered testing, keyword-driven, data-driven, and CI integration patterns.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nQA engineers, developers, and test architects use this skill to plan automation architecture before writing tests, including framework selection, test layering, test data separation, maintainability, and CI integration.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Users may include real production customer, payment, identity, or financial data in QA examples.\n\nMitigation: Use synthetic or redacted test data and mask sensitive identifiers, payment values, screenshots, and financial details before sharing examples.\n\nRisk: When Bash is available, project inspection commands may expose more workspace context than needed for architecture planning.\n\nMitigation: Keep command use user-directed and limited to inspecting project structure needed for the automation architecture.\n\n## Reference(s):\n\n\n## Skill Output:\n\n**Output Type(s):** [guidance, markdown, configuration]\n\n**Output Format:** [Markdown guidance with structured architecture sections and examples]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Outputs architecture design, framework selection, layer design, maintenance strategy, and CI integration guidance; designs include traceability IDs.]\n\n## Skill Version(s):\n\n1.6.3 (source: frontmatter and server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.6.0: 3 files, 5278 bytes\n\nFiles: skill-card.md (2557b), SKILL.md (8075b), _meta.json (142b)\n\nFile v1.6.0:SKILL.md\n\n---\r\nname: qa-test-automation-arch\r\nversion: 1.6.0\r\ndescription: >-\r\n 当需要设计自动化测试框架、或者现有框架维护成本太高需要重构时使用此技能。运用 PageObject、分层测试、关键字驱动、数据驱动等模式设计可维护可扩展的自动化架构。不要直接写测试代码——先设计架构：选型（UI/API/单元）、分层（测试层/业务层/基础设施层）、数据管理（测试数据与脚本分离）和 CI 集成方案。好的自动化架构应该让写用例的人不需要懂底层实现。\r\n\r\nwhen_to_use: 用户说\"自动化架构\"、\"框架设计\"、\"自动化策略\"、\"自动化框架\"、\"测试框架架构\"、需要设计测试自动化架构、自动化维护困难需要重构时\r\nallowed-tools: Read Grep Glob Bash\r\nrelated_skills:\r\n upstream:\r\n - qa-tech-selection # 输入：技术选型结果\r\n - qa-test-strategy-design # 输入：测试策略\r\n downstream:\r\n - qa-ci-cd-testing # 输出：架构设计用于CI/CD集成\r\n - qa-api-testing # 输出：架构设计指导API测试\r\n - qa-mobile-testing\r\n - qa-tech-debt-management\r\ninput_format:\r\n required:\r\n - name: 测试策略\r\n type: object\r\n description: 来自qa-test-strategy-design的测试策略\r\n - name: 技术选型\r\n type: object\r\n description: 来自qa-tech-selection的技术选型建议\r\n optional:\r\n - name: 项目约束\r\n type: string\r\n description: 技术栈和团队限制\r\noutput_format:\r\n traceability:\r\n - 每份架构设计带唯一ID（ARCH-XXXX）\r\n structure:\r\n - automation_architecture: 自动化测试架构设计\r\n - framework_selection: 框架选择建议\r\n - layer_design: 分层设计\r\n - maintenance_strategy: 维护策略\r\ncategories: ['Development','Testing','DevOps']\r\ndepth_requirement_quantification:\r\n reference_value: \"根据架构复杂度调整设计深度：简单×1/中等×2/复杂×3\"\r\n minimum: \"至少覆盖层架构、工具集成、维护策略3个核心要素\"\r\nerror_recovery_guidance:\r\n on_failure: \"自动化架构遗漏维护策略时回退到技术选型补充\"\r\n retry_behavior: \"补充选型后重新设计架构\"\r\n---\r\n> **⚠️ 安全警告**：本技能的示例可能涉及订单号、支付金额、截图、身份证、手机号等敏感数据。\r\n> 实际使用时请勿粘贴真实生产数据、客户信息或财务凭证；测试前应脱敏/掩码处理。\r\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\r\n\r\n# 测试自动化架构设计\r\n\r\n## 核心原则\r\n\r\n好的自动化架构——分层清晰、职责单一、易于维护、快速反馈。\r\n\r\n## 测试自动化金字塔\r\n\r\n> 📌 本节与 qa-test-strategy-design「测试金字塔」概念对应，但分层名称和比例不同——本技能侧重自动化落地（集成测试层名、70/20/10 比例），strategy-design 侧重策略规划（接口测试层名、60/30/10 比例）。修改时请确认两处含义，避免矛盾。\r\n\r\n```text\r\n ┌─────────────┐\r\n │ E2E测试 │ 10%\r\n │ (UI/API) │\r\n ├─────────────┤\r\n │ 集成测试 │ 20%\r\n │ (接口/服务) │\r\n ├─────────────┤\r\n │ 单元测试 │ 70%\r\n │ (函数/类) │\r\n └─────────────┘\r\n```\r\n\r\n## 分层架构设计\r\n\r\n### 第1层：单元测试层\r\n\r\n```text\r\n职责：\r\n├─ 测试范围：函数、类、模块\r\n├─ 执行速度：毫秒级\r\n├─ 维护成本：低\r\n└─ 覆盖目标：核心逻辑\r\n\r\n技术选型：\r\n├─ Java：JUnit 5 + Mockito\r\n├─ Python：Pytest + Mock\r\n├─ JavaScript：Jest + Sinon\r\n└─ Go：testing + testify\r\n\r\n最佳实践：\r\n├─ 测试与代码同步维护\r\n├─ 每个测试单一职责\r\n├─ 使用Mock隔离依赖\r\n├─ 测试命名清晰（Given-When-Then）\r\n└─ 保持测试快速（<100ms）\r\n```\r\n\r\n### 第2层：集成测试层\r\n\r\n```text\r\n职责：\r\n├─ 测试范围：接口、服务间交互\r\n├─ 执行速度：秒级\r\n├─ 维护成本：中\r\n└─ 覆盖目标：业务流程\r\n\r\n技术选型：\r\n├─ API测试：Postman/Newman/REST Assured\r\n├─ 数据库测试：TestContainers\r\n├─ 消息队列测试：Embedded Kafka\r\n└─ 服务虚拟化：WireMock/Mountebank\r\n\r\n最佳实践：\r\n├─ 使用真实依赖（TestContainers）\r\n├─ 测试数据可构造、可清理\r\n├─ 验证接口契约\r\n├─ 覆盖正常/异常/边界场景\r\n└─ 保持测试独立性\r\n```\r\n\r\n### 第3层：E2E测试层\r\n\r\n```text\r\n职责：\r\n├─ 测试范围：完整用户流程\r\n├─ 执行速度：分钟级\r\n├─ 维护成本：高\r\n└─ 覆盖目标：核心路径\r\n\r\n技术选型：\r\n├─ Web UI：Playwright/Cypress/Selenium\r\n├─ 移动端：Appium/XCUITest/Espresso\r\n├─ 桌面端：Electron Test/WinAppDriver\r\n└─ 性能：JMeter/Locust/k6\r\n\r\n最佳实践：\r\n├─ 只覆盖核心路径（20%）\r\n├─ 使用Page Object模式\r\n├─ 数据驱动测试\r\n├─ 稳定的等待策略\r\n└─ 失败时自动截图/录屏\r\n```\r\n\r\n## 框架设计模式\r\n\r\n### Page Object Model\r\n\r\n```text\r\n优点：\r\n├─ 封装页面元素和操作\r\n├─ 减少代码重复\r\n├─ 易于维护\r\n└─ 可读性强\r\n\r\n示例结构：\r\ntests/\r\n├── pages/\r\n│ ├── login_page.py\r\n│ ├── home_page.py\r\n│ └── cart_page.py\r\n├── tests/\r\n│ ├── test_login.py\r\n│ ├── test_home.py\r\n│ └── test_cart.py\r\n├── fixtures/\r\n│ ├── test_data.py\r\n│ └── setup_teardown.py\r\n└── utils/\r\n ├── driver_factory.py\r\n └── report_generator.py\r\n```\r\n\r\n### 关键字驱动\r\n\r\n```text\r\n优点：\r\n├─ 业务人员可参与\r\n├─ 测试用例可读性强\r\n├─ 与实现分离\r\n└─ 易于复用\r\n\r\n示例：\r\n| 关键字 | 参数1 | 参数2 | 参数3 |\r\n|--------|-------|-------|-------|\r\n| 打开浏览器 | Chrome | | |\r\n| 输入用户名 | testuser | | |\r\n| 输入密码 | Test@123 | | |\r\n| 点击登录 | | | |\r\n| 验证跳转 | /home | | |\r\n```\r\n\r\n### 数据驱动\r\n\r\n```text\r\n优点：\r\n├─ 测试数据与逻辑分离\r\n├─ 易于添加新用例\r\n├─ 覆盖多种场景\r\n└─ 便于维护\r\n\r\n示例：\r\n@pytest.mark.parametrize(\"username,password,expected\", [\r\n (\"user1\", \"pass1\", \"success\"),\r\n (\"user2\", \"pass2\", \"success\"),\r\n (\"\", \"pass3\", \"error\"),\r\n (\"user4\", \"\", \"error\"),\r\n])\r\ndef test_login(username, password, expected):\r\n result = login(username, password)\r\n assert result == expected\r\n```\r\n\r\n## 框架选型决策\r\n\r\n| 维度 | Playwright | Cypress | Selenium |\r\n|------|-----------|---------|----------|\r\n| 浏览器支持 | 多浏览器 | 仅Chrome | 多语言 |\r\n| 执行速度 | 快 | 快 | 中等 |\r\n| 调试体验 | 好 | 优秀 | 一般 |\r\n| 学习曲线 | 中等 | 低 | 高 |\r\n| 社区生态 | 成长中 | 成熟 | 成熟 |\r\n| 适用场景 | 现代Web | 单页应用 | 传统Web |\r\n\r\n## 输出示例\r\n\r\n**设计Web UI自动化框架（团队5人，JS技术栈，1000+用例）**\r\n→ 分层：单元测试（Jest）→集成测试（Supertest）→E2E（Playwright）\r\n→ 模式：Page Object Model组织页面对象，关键字驱动封装业务操作\r\n→ 数据驱动：JSON/CSV管理测试数据，和环境配置分离\r\n→ CI/CD集成：GitHub Actions触发，Allure报告\r\n\r\n**API自动化框架设计**\r\n→ 分层：请求封装层→业务接口层→用例层→数据层\r\n\r\n## 检查清单\r\n\r\n架构设计完成后检查：\r\n- [ ] 分层是否清晰（单元/集成/E2E）？\r\n- [ ] 各层职责是否明确？\r\n- [ ] 框架选型是否合理？\r\n- [ ] 设计模式是否适用？\r\n- [ ] 可维护性是否考虑？\r\n- [ ] CI/CD集成是否规划？\n\nFile v1.6.0:_meta.json\n\n{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-test-automation-arch\",\n \"version\": \"1.6.0\",\n \"publishedAt\": 1783358303794\n}\n\nFile v1.6.0:skill-card.md\n\n## Description:
\nHelps teams design maintainable QA test automation architecture using patterns such as Page Object, layered testing, keyword-driven testing, data-driven testing, test data separation, and CI integration planning.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[kokxi](https://clawhub.ai/user/kokxi)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nQA engineers, developers, and test automation leads use this skill when designing or refactoring automation frameworks for UI, API, unit, integration, E2E, mobile, and CI/CD testing. It is intended to produce architecture guidance before test implementation, including framework selection, layer design, maintenance strategy, and traceable ARCH-XXXX design identifiers.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Users may paste real customer, payment, identity, production, or screenshot data while asking for QA architecture help.
\nMitigation: Use anonymized or synthetic examples and redact sensitive values before sharing project context with the agent.
\nRisk: Architecture guidance may be incomplete or mismatched to the project if the input strategy, technology selection, or constraints are underspecified.
\nMitigation: Review the proposed architecture before implementation and ensure it covers layer architecture, tool integration, and maintenance strategy.
\nRisk: The skill allows project inspection tools and Bash when the hosting agent enables them.
\nMitigation: Run the skill in a controlled workspace and review any proposed shell commands before execution.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/kokxi/skills/qa-test-automation-arch)
\n\n\n## Skill Output:
\n**Output Type(s):** [guidance, markdown, configuration]
\n**Output Format:** [Markdown architecture guidance with structured sections and checklists]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Outputs should include a unique ARCH-XXXX traceability identifier and cover layer architecture, tool integration, and maintenance strategy.]
\n\n## Skill Version(s):
\n1.6.0 (source: frontmatter and server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.5.0: 3 files, 4653 bytes\n\nFiles: skill-card.md (2181b), SKILL.md (7376b), _meta.json (142b)\n\nFile v1.5.0:SKILL.md\n\n---\r\nname: qa-test-automation-arch\r\nversion: 1.5.0\r\ndescription: >-\r\n 当需要设计自动化测试框架、或者现有框架维护成本太高需要重构时使用此技能。运用 PageObject、分层测试、关键字驱动、数据驱动等模式设计可维护可扩展的自动化架构。不要直接写测试代码——先设计架构：选型（UI/API/单元）、分层（测试层/业务层/基础设施层）、数据管理（测试数据与脚本分离）和 CI 集成方案。好的自动化架构应该让写用例的人不需要懂底层实现。\r\n\r\nwhen_to_use: 用户说\"自动化架构\"、\"框架设计\"、\"自动化策略\"、\"自动化框架\"、\"测试框架\"、需要设计测试自动化架构、自动化维护困难需要重构时\r\nallowed-tools: Read Grep Glob Bash\r\nrelated_skills:\r\n upstream:\r\n - qa-tech-selection # 输入：技术选型结果\r\n - qa-test-strategy-design # 输入：测试策略\r\n downstream:\r\n - qa-ci-cd-testing # 输出：架构设计用于CI/CD集成\r\n - qa-api-testing # 输出：架构设计指导API测试\r\ninput_format:\r\n required:\r\n - name: 测试策略\r\n type: object\r\n description: 来自qa-test-strategy-design的测试策略\r\n - name: 技术选型\r\n type: object\r\n description: 来自qa-tech-selection的技术选型建议\r\n optional:\r\n - name: 项目约束\r\n type: string\r\n description: 技术栈和团队限制\r\noutput_format:\r\n structure:\r\n - automation_architecture: 自动化测试架构设计\r\n - framework_selection: 框架选择建议\r\n - layer_design: 分层设计\r\n - maintenance_strategy: 维护策略\r\n---\r\n\r\n# 测试自动化架构设计\r\n\r\n## 核心原则\r\n\r\n你是一位自动化架构专家，擅长设计可维护、可扩展的自动化测试框架。\r\n**核心原则**：好的自动化架构——分层清晰、职责单一、易于维护、快速反馈。\r\n本技能覆盖自动化金字塔、分层架构、设计模式和框架选型。\r\n\r\n## 测试自动化金字塔\r\n\r\n> 📌 本节与 qa-test-strategy-design「测试金字塔」概念对应，但分层名称和比例不同——本技能侧重自动化落地（集成测试层名、70/20/10 比例），strategy-design 侧重策略规划（接口测试层名、60/30/10 比例）。修改时请确认两处含义，避免矛盾。\r\n\r\n```text\r\n ┌─────────────┐\r\n │ E2E测试 │ 10%\r\n │ (UI/API) │\r\n ├─────────────┤\r\n │ 集成测试 │ 20%\r\n │ (接口/服务) │\r\n ├─────────────┤\r\n │ 单元测试 │ 70%\r\n │ (函数/类) │\r\n └─────────────┘\r\n```\r\n\r\n## 分层架构设计\r\n\r\n### 第1层：单元测试层\r\n\r\n```text\r\n职责：\r\n├─ 测试范围：函数、类、模块\r\n├─ 执行速度：毫秒级\r\n├─ 维护成本：低\r\n└─ 覆盖目标：核心逻辑\r\n\r\n技术选型：\r\n├─ Java：JUnit 5 + Mockito\r\n├─ Python：Pytest + Mock\r\n├─ JavaScript：Jest + Sinon\r\n└─ Go：testing + testify\r\n\r\n最佳实践：\r\n├─ 测试与代码同步维护\r\n├─ 每个测试单一职责\r\n├─ 使用Mock隔离依赖\r\n├─ 测试命名清晰（Given-When-Then）\r\n└─ 保持测试快速（<100ms）\r\n```\r\n\r\n### 第2层：集成测试层\r\n\r\n```text\r\n职责：\r\n├─ 测试范围：接口、服务间交互\r\n├─ 执行速度：秒级\r\n├─ 维护成本：中\r\n└─ 覆盖目标：业务流程\r\n\r\n技术选型：\r\n├─ API测试：Postman/Newman/REST Assured\r\n├─ 数据库测试：TestContainers\r\n├─ 消息队列测试：Embedded Kafka\r\n└─ 服务虚拟化：WireMock/Mountebank\r\n\r\n最佳实践：\r\n├─ 使用真实依赖（TestContainers）\r\n├─ 测试数据可构造、可清理\r\n├─ 验证接口契约\r\n├─ 覆盖正常/异常/边界场景\r\n└─ 保持测试独立性\r\n```\r\n\r\n### 第3层：E2E测试层\r\n\r\n```text\r\n职责：\r\n├─ 测试范围：完整用户流程\r\n├─ 执行速度：分钟级\r\n├─ 维护成本：高\r\n└─ 覆盖目标：核心路径\r\n\r\n技术选型：\r\n├─ Web UI：Playwright/Cypress/Selenium\r\n├─ 移动端：Appium/XCUITest/Espresso\r\n├─ 桌面端：Electron Test/WinAppDriver\r\n└─ 性能：JMeter/Locust/k6\r\n\r\n最佳实践：\r\n├─ 只覆盖核心路径（20%）\r\n├─ 使用Page Object模式\r\n├─ 数据驱动测试\r\n├─ 稳定的等待策略\r\n└─ 失败时自动截图/录屏\r\n```\r\n\r\n## 框架设计模式\r\n\r\n### Page Object Model\r\n\r\n```text\r\n优点：\r\n├─ 封装页面元素和操作\r\n├─ 减少代码重复\r\n├─ 易于维护\r\n└─ 可读性强\r\n\r\n示例结构：\r\ntests/\r\n├── pages/\r\n│ ├── login_page.py\r\n│ ├── home_page.py\r\n│ └── cart_page.py\r\n├── tests/\r\n│ ├── test_login.py\r\n│ ├── test_home.py\r\n│ └── test_cart.py\r\n├── fixtures/\r\n│ ├── test_data.py\r\n│ └── setup_teardown.py\r\n└── utils/\r\n ├── driver_factory.py\r\n └── report_generator.py\r\n```\r\n\r\n### 关键字驱动\r\n\r\n```text\r\n优点：\r\n├─ 业务人员可参与\r\n├─ 测试用例可读性强\r\n├─ 与实现分离\r\n└─ 易于复用\r\n\r\n示例：\r\n| 关键字 | 参数1 | 参数2 | 参数3 |\r\n|--------|-------|-------|-------|\r\n| 打开浏览器 | Chrome | | |\r\n| 输入用户名 | testuser | | |\r\n| 输入密码 | Test@123 | | |\r\n| 点击登录 | | | |\r\n| 验证跳转 | /home | | |\r\n```\r\n\r\n### 数据驱动\r\n\r\n```text\r\n优点：\r\n├─ 测试数据与逻辑分离\r\n├─ 易于添加新用例\r\n├─ 覆盖多种场景\r\n└─ 便于维护\r\n\r\n示例：\r\n@pytest.mark.parametrize(\"username,password,expected\", [\r\n (\"user1\", \"pass1\", \"success\"),\r\n (\"user2\", \"pass2\", \"success\"),\r\n (\"\", \"pass3\", \"error\"),\r\n (\"user4\", \"\", \"error\"),\r\n])\r\ndef test_login(username, password, expected):\r\n result = login(username, password)\r\n assert result == expected\r\n```\r\n\r\n## 框架选型决策\r\n\r\n| 维度 | Playwright | Cypress | Selenium |\r\n|------|-----------|---------|----------|\r\n| 浏览器支持 | 多浏览器 | 仅Chrome | 多语言 |\r\n| 执行速度 | 快 | 快 | 中等 |\r\n| 调试体验 | 好 | 优秀 | 一般 |\r\n| 学习曲线 | 中等 | 低 | 高 |\r\n| 社区生态 | 成长中 | 成熟 | 成熟 |\r\n| 适用场景 | 现代Web | 单页应用 | 传统Web |\r\n\r\n## 输出示例\r\n\r\n**设计Web UI自动化框架（团队5人，JS技术栈，1000+用例）**\r\n→ 分层：单元测试（Jest）→集成测试（Supertest）→E2E（Playwright）\r\n→ 模式：Page Object Model组织页面对象，关键字驱动封装业务操作\r\n→ 数据驱动：JSON/CSV管理测试数据，和环境配置分离\r\n→ CI/CD集成：GitHub Actions触发，Allure报告\r\n\r\n**API自动化框架设计**\r\n→ 分层：请求封装层→业务接口层→用例层→数据层\r\n\r\n## 检查清单\r\n\r\n架构设计完成后检查：\r\n- [ ] 分层是否清晰（单元/集成/E2E）？\r\n- [ ] 各层职责是否明确？\r\n- [ ] 框架选型是否合理？\r\n- [ ] 设计模式是否适用？\r\n- [ ] 可维护性是否考虑？\r\n- [ ] CI/CD集成是否规划？\n\nFile v1.5.0:_meta.json\n\n{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-test-automation-arch\",\n \"version\": \"1.5.0\",\n \"publishedAt\": 1782736581631\n}\n\nFile v1.5.0:skill-card.md\n\n## Description:
\nProvides guidance for designing maintainable QA test automation architectures using layered testing, Page Object, keyword-driven, data-driven, test data management, and CI integration patterns before writing test code.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[kokxi](https://clawhub.ai/user/kokxi)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers, QA engineers, and test architects use this skill to design or refactor automation frameworks for UI, API, integration, and unit testing before implementing test cases. It is best suited for architecture and framework design rather than one-off test-case generation.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill may activate on broad testing-framework requests when the user only wants a single test case, CI/CD change, or general test strategy.
\nMitigation: State the desired scope explicitly, such as automation architecture design, single-test implementation, CI/CD integration, or test strategy.
\nRisk: Architecture recommendations may not fit the project's existing technology stack, team constraints, or maintenance capacity.
\nMitigation: Review the proposed framework, layers, data strategy, and CI integration against project constraints before implementation.
\n\n\n## Reference(s):
\n\n\n## Skill Output:
\n**Output Type(s):** [Guidance, Markdown, Configuration]
\n**Output Format:** [Markdown with structured architecture recommendations, framework selection guidance, layer design, maintenance strategy, and checklists]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Produces architecture guidance rather than directly writing test code.]
\n\n## Skill Version(s):
\n1.5.0 (source: skill frontmatter and release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.4.1: 3 files, 4184 bytes\n\nFiles: skill-card.md (2185b), SKILL.md (6250b), _meta.json (142b)\n\nFile v1.4.1:SKILL.md\n\n---\r\nname: qa-test-automation-arch\r\ndescription: >-\r\n 测试自动化架构设计，运用PageObject/分层/关键字驱动等模式构建可维护可扩展的自动化框架。当需要设计或优化自动化测试架构时激活。\r\n\r\nwhen_to_use: 用户说\"自动化架构\"、\"框架设计\"、\"自动化策略\"、\"自动化框架\"、\"测试框架\"、需要设计测试自动化架构、自动化维护困难需要重构时\r\nallowed-tools: Read Grep Glob Bash\r\nrelated_skills:\r\n upstream:\r\n - qa-tech-selection # 输入：技术选型结果\r\n - qa-test-strategy-design # 输入：测试策略\r\n downstream:\r\n - qa-ci-cd-testing # 输出：架构设计用于CI/CD集成\r\n - qa-api-testing # 输出：架构设计指导API测试\r\ninput_format: 技术选型 + 测试策略\r\noutput_format: 自动化架构设计（分层策略+框架选型+最佳实践）\r\n---\r\n\r\n# 测试自动化架构设计\r\n\r\n## Overview\r\n\r\n你是一位自动化架构专家，擅长设计可维护、可扩展的自动化测试框架。\r\n**核心原则**：好的自动化架构——分层清晰、职责单一、易于维护、快速反馈。\r\n本技能覆盖自动化金字塔、分层架构、设计模式和框架选型。\r\n\r\n## 测试自动化金字塔\r\n\r\n```\r\n ┌─────────────┐\r\n │ E2E测试 │ 10%\r\n │ (UI/API) │\r\n ├─────────────┤\r\n │ 集成测试 │ 20%\r\n │ (接口/服务) │\r\n ├─────────────┤\r\n │ 单元测试 │ 70%\r\n │ (函数/类) │\r\n └─────────────┘\r\n```\r\n\r\n## 分层架构设计\r\n\r\n### 第1层：单元测试层\r\n\r\n```\r\n职责：\r\n├─ 测试范围：函数、类、模块\r\n├─ 执行速度：毫秒级\r\n├─ 维护成本：低\r\n└─ 覆盖目标：核心逻辑\r\n\r\n技术选型：\r\n├─ Java：JUnit 5 + Mockito\r\n├─ Python：Pytest + Mock\r\n├─ JavaScript：Jest + Sinon\r\n└─ Go：testing + testify\r\n\r\n最佳实践：\r\n├─ 测试与代码同步维护\r\n├─ 每个测试单一职责\r\n├─ 使用Mock隔离依赖\r\n├─ 测试命名清晰（Given-When-Then）\r\n└─ 保持测试快速（<100ms）\r\n```\r\n\r\n### 第2层：集成测试层\r\n\r\n```\r\n职责：\r\n├─ 测试范围：接口、服务间交互\r\n├─ 执行速度：秒级\r\n├─ 维护成本：中\r\n└─ 覆盖目标：业务流程\r\n\r\n技术选型：\r\n├─ API测试：Postman/Newman/REST Assured\r\n├─ 数据库测试：TestContainers\r\n├─ 消息队列测试：Embedded Kafka\r\n└─ 服务虚拟化：WireMock/Mountebank\r\n\r\n最佳实践：\r\n├─ 使用真实依赖（TestContainers）\r\n├─ 测试数据可构造、可清理\r\n├─ 验证接口契约\r\n├─ 覆盖正常/异常/边界场景\r\n└─ 保持测试独立性\r\n```\r\n\r\n### 第3层：E2E测试层\r\n\r\n```\r\n职责：\r\n├─ 测试范围：完整用户流程\r\n├─ 执行速度：分钟级\r\n├─ 维护成本：高\r\n└─ 覆盖目标：核心路径\r\n\r\n技术选型：\r\n├─ Web UI：Playwright/Cypress/Selenium\r\n├─ 移动端：Appium/XCUITest/Espresso\r\n├─ 桌面端：Electron Test/WinAppDriver\r\n└─ 性能：JMeter/Locust/k6\r\n\r\n最佳实践：\r\n├─ 只覆盖核心路径（20%）\r\n├─ 使用Page Object模式\r\n├─ 数据驱动测试\r\n├─ 稳定的等待策略\r\n└─ 失败时自动截图/录屏\r\n```\r\n\r\n## 框架设计模式\r\n\r\n### Page Object Model\r\n\r\n```\r\n优点：\r\n├─ 封装页面元素和操作\r\n├─ 减少代码重复\r\n├─ 易于维护\r\n└─ 可读性强\r\n\r\n示例结构：\r\ntests/\r\n├── pages/\r\n│ ├── login_page.py\r\n│ ├── home_page.py\r\n│ └── cart_page.py\r\n├── tests/\r\n│ ├── test_login.py\r\n│ ├── test_home.py\r\n│ └── test_cart.py\r\n├── fixtures/\r\n│ ├── test_data.py\r\n│ └── setup_teardown.py\r\n└── utils/\r\n ├── driver_factory.py\r\n └── report_generator.py\r\n```\r\n\r\n### 关键字驱动\r\n\r\n```\r\n优点：\r\n├─ 业务人员可参与\r\n├─ 测试用例可读性强\r\n├─ 与实现分离\r\n└─ 易于复用\r\n\r\n示例：\r\n| 关键字 | 参数1 | 参数2 | 参数3 |\r\n|--------|-------|-------|-------|\r\n| 打开浏览器 | Chrome | | |\r\n| 输入用户名 | testuser | | |\r\n| 输入密码 | Test@123 | | |\r\n| 点击登录 | | | |\r\n| 验证跳转 | /home | | |\r\n```\r\n\r\n### 数据驱动\r\n\r\n```\r\n优点：\r\n├─ 测试数据与逻辑分离\r\n├─ 易于添加新用例\r\n├─ 覆盖多种场景\r\n└─ 便于维护\r\n\r\n示例：\r\n@pytest.mark.parametrize(\"username,password,expected\", [\r\n (\"user1\", \"pass1\", \"success\"),\r\n (\"user2\", \"pass2\", \"success\"),\r\n (\"\", \"pass3\", \"error\"),\r\n (\"user4\", \"\", \"error\"),\r\n])\r\ndef test_login(username, password, expected):\r\n result = login(username, password)\r\n assert result == expected\r\n```\r\n\r\n## 框架选型决策\r\n\r\n| 维度 | Playwright | Cypress | Selenium |\r\n|------|-----------|---------|----------|\r\n| 浏览器支持 | 多浏览器 | 仅Chrome | 多语言 |\r\n| 执行速度 | 快 | 快 | 中等 |\r\n| 调试体验 | 好 | 优秀 | 一般 |\r\n| 学习曲线 | 中等 | 低 | 高 |\r\n| 社区生态 | 成长中 | 成熟 | 成熟 |\r\n| 适用场景 | 现代Web | 单页应用 | 传统Web |\r\n\r\n## Examples\r\n\r\n**设计Web UI自动化框架（团队5人，JS技术栈，1000+用例）**\r\n→ 分层：单元测试（Jest）→集成测试（Supertest）→E2E（Playwright）\r\n→ 模式：Page Object Model组织页面对象，关键字驱动封装业务操作\r\n→ 数据驱动：JSON/CSV管理测试数据，和环境配置分离\r\n→ CI/CD集成：GitHub Actions触发，Allure报告\r\n\r\n**API自动化框架设计**\r\n→ 分层：请求封装层→业务接口层→用例层→数据层\r\n\r\n## Guidelines\r\n\r\n架构设计完成后检查：\r\n- [ ] 分层是否清晰（单元/集成/E2E）？\r\n- [ ] 各层职责是否明确？\r\n- [ ] 框架选型是否合理？\r\n- [ ] 设计模式是否适用？\r\n- [ ] 可维护性是否考虑？\r\n- [ ] CI/CD集成是否规划？\n\nFile v1.4.1:_meta.json\n\n{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-test-automation-arch\",\n \"version\": \"1.4.1\",\n \"publishedAt\": 1782406636135\n}\n\nFile v1.4.1:skill-card.md\n\n## Description:
\nProvides Chinese-language guidance for designing maintainable, scalable test automation frameworks using test pyramids, layered architecture, Page Object, keyword-driven, and data-driven patterns.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[kokxi](https://clawhub.ai/user/kokxi)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nQA engineers, test automation architects, and development teams use this skill to design or optimize automated testing architecture, including test layering, framework selection, design patterns, and CI/CD integration planning.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill may activate on general architecture phrases beyond test automation architecture.
\nMitigation: Confirm the request is about test automation architecture before applying the skill's guidance.
\nRisk: Bash is listed as an allowed tool even though the skill itself does not require command execution.
\nMitigation: Review any proposed shell command before execution and prefer non-executing architecture guidance unless a command is clearly needed.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/kokxi/skills/qa-test-automation-arch)
\n- [ClawHub publisher profile](https://clawhub.ai/user/kokxi)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with structured recommendations and example code, command, or configuration snippets when useful.]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May include layered testing strategy, framework comparisons, design-pattern guidance, and CI/CD integration recommendations.]
\n\n## Skill Version(s):
\n1.4.1 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.4.0: 3 files, 4394 bytes\n\nFiles: skill-card.md (2480b), SKILL.md (6533b), _meta.json (142b)\n\nFile v1.4.0:SKILL.md\n\n---\r\nname: qa-test-automation-arch\r\ndescription: >-\r\n 测试自动化架构设计，设计可维护、可扩展的自动化测试框架。当用户需要设计或优化自动化测试架构、设计框架或制定自动化策略时自动触发。\r\n 也适用于：自动化测试维护困难需要重构架构，或新建项目需要搭建自动化框架时。\r\n 关键词：自动化架构、框架设计、分层策略、可维护性、Page Object、关键字驱动、数据驱动、持续集成、自动化测试框架。\nwhen_to_use: 用户说\"自动化架构\"、\"框架设计\"、\"自动化策略\"、\"自动化框架\"、\"测试框架\"、需要设计测试自动化架构、自动化维护困难需要重构时\r\nallowed-tools: Read Grep Glob Bash\r\nrelated_skills:\r\n upstream:\r\n - qa-tech-selection # 输入：技术选型结果\r\n - qa-test-strategy-design # 输入：测试策略\r\n downstream:\r\n - qa-ci-cd-testing # 输出：架构设计用于CI/CD集成\r\n - qa-api-testing # 输出：架构设计指导API测试\r\ninput_format: 技术选型 + 测试策略\r\noutput_format: 自动化架构设计（分层策略+框架选型+最佳实践）\r\n---\r\n\r\n# 测试自动化架构设计\r\n\r\n## Overview\r\n\r\n你是一位自动化架构专家，擅长设计可维护、可扩展的自动化测试框架。\r\n**核心原则**：好的自动化架构——分层清晰、职责单一、易于维护、快速反馈。\r\n本技能覆盖自动化金字塔、分层架构、设计模式和框架选型。\r\n\r\n## 测试自动化金字塔\r\n\r\n```\r\n ┌─────────────┐\r\n │ E2E测试 │ 10%\r\n │ (UI/API) │\r\n ├─────────────┤\r\n │ 集成测试 │ 20%\r\n │ (接口/服务) │\r\n ├─────────────┤\r\n │ 单元测试 │ 70%\r\n │ (函数/类) │\r\n └─────────────┘\r\n```\r\n\r\n## 分层架构设计\r\n\r\n### 第1层：单元测试层\r\n\r\n```\r\n职责：\r\n├─ 测试范围：函数、类、模块\r\n├─ 执行速度：毫秒级\r\n├─ 维护成本：低\r\n└─ 覆盖目标：核心逻辑\r\n\r\n技术选型：\r\n├─ Java：JUnit 5 + Mockito\r\n├─ Python：Pytest + Mock\r\n├─ JavaScript：Jest + Sinon\r\n└─ Go：testing + testify\r\n\r\n最佳实践：\r\n├─ 测试与代码同步维护\r\n├─ 每个测试单一职责\r\n├─ 使用Mock隔离依赖\r\n├─ 测试命名清晰（Given-When-Then）\r\n└─ 保持测试快速（<100ms）\r\n```\r\n\r\n### 第2层：集成测试层\r\n\r\n```\r\n职责：\r\n├─ 测试范围：接口、服务间交互\r\n├─ 执行速度：秒级\r\n├─ 维护成本：中\r\n└─ 覆盖目标：业务流程\r\n\r\n技术选型：\r\n├─ API测试：Postman/Newman/REST Assured\r\n├─ 数据库测试：TestContainers\r\n├─ 消息队列测试：Embedded Kafka\r\n└─ 服务虚拟化：WireMock/Mountebank\r\n\r\n最佳实践：\r\n├─ 使用真实依赖（TestContainers）\r\n├─ 测试数据可构造、可清理\r\n├─ 验证接口契约\r\n├─ 覆盖正常/异常/边界场景\r\n└─ 保持测试独立性\r\n```\r\n\r\n### 第3层：E2E测试层\r\n\r\n```\r\n职责：\r\n├─ 测试范围：完整用户流程\r\n├─ 执行速度：分钟级\r\n├─ 维护成本：高\r\n└─ 覆盖目标：核心路径\r\n\r\n技术选型：\r\n├─ Web UI：Playwright/Cypress/Selenium\r\n├─ 移动端：Appium/XCUITest/Espresso\r\n├─ 桌面端：Electron Test/WinAppDriver\r\n└─ 性能：JMeter/Locust/k6\r\n\r\n最佳实践：\r\n├─ 只覆盖核心路径（20%）\r\n├─ 使用Page Object模式\r\n├─ 数据驱动测试\r\n├─ 稳定的等待策略\r\n└─ 失败时自动截图/录屏\r\n```\r\n\r\n## 框架设计模式\r\n\r\n### Page Object Model\r\n\r\n```\r\n优点：\r\n├─ 封装页面元素和操作\r\n├─ 减少代码重复\r\n├─ 易于维护\r\n└─ 可读性强\r\n\r\n示例结构：\r\ntests/\r\n├── pages/\r\n│ ├── login_page.py\r\n│ ├── home_page.py\r\n│ └── cart_page.py\r\n├── tests/\r\n│ ├── test_login.py\r\n│ ├── test_home.py\r\n│ └── test_cart.py\r\n├── fixtures/\r\n│ ├── test_data.py\r\n│ └── setup_teardown.py\r\n└── utils/\r\n ├── driver_factory.py\r\n └── report_generator.py\r\n```\r\n\r\n### 关键字驱动\r\n\r\n```\r\n优点：\r\n├─ 业务人员可参与\r\n├─ 测试用例可读性强\r\n├─ 与实现分离\r\n└─ 易于复用\r\n\r\n示例：\r\n| 关键字 | 参数1 | 参数2 | 参数3 |\r\n|--------|-------|-------|-------|\r\n| 打开浏览器 | Chrome | | |\r\n| 输入用户名 | testuser | | |\r\n| 输入密码 | Test@123 | | |\r\n| 点击登录 | | | |\r\n| 验证跳转 | /home | | |\r\n```\r\n\r\n### 数据驱动\r\n\r\n```\r\n优点：\r\n├─ 测试数据与逻辑分离\r\n├─ 易于添加新用例\r\n├─ 覆盖多种场景\r\n└─ 便于维护\r\n\r\n示例：\r\n@pytest.mark.parametrize(\"username,password,expected\", [\r\n (\"user1\", \"pass1\", \"success\"),\r\n (\"user2\", \"pass2\", \"success\"),\r\n (\"\", \"pass3\", \"error\"),\r\n (\"user4\", \"\", \"error\"),\r\n])\r\ndef test_login(username, password, expected):\r\n result = login(username, password)\r\n assert result == expected\r\n```\r\n\r\n## 框架选型决策\r\n\r\n| 维度 | Playwright | Cypress | Selenium |\r\n|------|-----------|---------|----------|\r\n| 浏览器支持 | 多浏览器 | 仅Chrome | 多语言 |\r\n| 执行速度 | 快 | 快 | 中等 |\r\n| 调试体验 | 好 | 优秀 | 一般 |\r\n| 学习曲线 | 中等 | 低 | 高 |\r\n| 社区生态 | 成长中 | 成熟 | 成熟 |\r\n| 适用场景 | 现代Web | 单页应用 | 传统Web |\r\n\r\n## Examples\r\n\r\n**设计Web UI自动化框架（团队5人，JS技术栈，1000+用例）**\r\n→ 分层：单元测试（Jest）→集成测试（Supertest）→E2E（Playwright）\r\n→ 模式：Page Object Model组织页面对象，关键字驱动封装业务操作\r\n→ 数据驱动：JSON/CSV管理测试数据，和环境配置分离\r\n→ CI/CD集成：GitHub Actions触发，Allure报告\r\n\r\n**API自动化框架设计**\r\n→ 分层：请求封装层→业务接口层→用例层→数据层\r\n\r\n## Guidelines\r\n\r\n架构设计完成后检查：\r\n- [ ] 分层是否清晰（单元/集成/E2E）？\r\n- [ ] 各层职责是否明确？\r\n- [ ] 框架选型是否合理？\r\n- [ ] 设计模式是否适用？\r\n- [ ] 可维护性是否考虑？\r\n- [ ] CI/CD集成是否规划？\n\nFile v1.4.0:_meta.json\n\n{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-test-automation-arch\",\n \"version\": \"1.4.0\",\n \"publishedAt\": 1782277992771\n}\n\nFile v1.4.0:skill-card.md\n\n## Description:
\nProvides Chinese-language guidance for designing maintainable, scalable automated testing architectures, including layered testing strategy, framework selection, design patterns, and CI/CD considerations.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[kokxi](https://clawhub.ai/user/kokxi)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nQA engineers, test automation architects, and developers use this skill to design or refactor automated testing frameworks across unit, integration, API, UI, and E2E layers.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill may trigger on broad framework-design requests and provide testing architecture guidance without enough project context.
\nMitigation: Ask for the user's technology stack, team size, test scope, CI/CD constraints, and current maintenance pain points before applying recommendations.
\nRisk: Because Bash is allowed, the agent may propose shell commands while helping implement or inspect a testing framework.
\nMitigation: Review proposed shell commands before execution and avoid running commands that modify files, install packages, or contact external services unless the user has approved that action.
\nRisk: Architecture recommendations can be incorrect or misleading if treated as final without validating them against the product, risk profile, and test data constraints.
\nMitigation: Have a QA or engineering reviewer confirm the proposed layers, framework choices, and CI/CD integration plan before adoption.
\n\n\n## Reference(s):
\n\n\n## Skill Output:
\n**Output Type(s):** [Guidance, Markdown, Configuration, Code]
\n**Output Format:** [Markdown text with architecture recommendations, framework comparisons, checklists, and occasional code or configuration examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Chinese-language output; may include shell command suggestions because Bash is allowed, so commands should be reviewed before execution.]
\n\n## Skill Version(s):
\n1.4.0 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
","readmeExcerpt":"Skill: qa-test-automation-arch Owner: kokxi Summary: 当需要设计自动化测试框架、或者现有框架维护成本太高需要重构时使用此技能。运用 PageObject、分层测试、关键字驱动、数据驱动等模式设计可维护可扩展的自动化架构。不要直接写测试代码——先设计架构：选型（UI/API/单元）、分层（测试层/业务层/基础设施层）、数据管理（测试数据与脚本分离）和 CI 集成方案。好的自动化架构应该让写用例的人不需要懂底层实现。 触发场景：自动化架构、框架设计、自动化策略、自动化框架、测试框架架构、自动化维护困难需要重构时。 Use when the user asks about: test automation architecture — Page Object, layered test design, keyword-driven and data-driven frameworks","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"┌─────────────┐\n │ E2E测试 │ 10%\n │ (UI/API) │\n ├─────────────┤\n │ 集成测试 │ 20%\n │ (接口/服务) │\n ├─────────────┤\n │ 单元测试 │ 70%\n │ (函数/类) │\n └─────────────┘"},{"language":"text","snippet":"优点：\n├─ 封装页面元素和操作\n├─ 减少代码重复\n├─ 易于维护\n└─ 可读性强\n\n示例结构：\ntests/\n├── pages/\n│ ├── login_page.py\n│ ├── home_page.py\n│ └── cart_page.py\n├── tests/\n│ ├── test_login.py\n│ ├── test_home.py\n│ └── test_cart.py\n├── fixtures/\n│ ├── test_data.py\n│ └── setup_teardown.py\n└── utils/\n ├── driver_factory.py\n └── report_generator.py"},{"language":"text","snippet":"优点：\n├─ 业务人员可参与\n├─ 测试用例可读性强\n├─ 与实现分离\n└─ 易于复用\n\n示例：\n| 关键字 | 参数1 | 参数2 | 参数3 |\n|--------|-------|-------|-------|\n| 打开浏览器 | Chrome | | |\n| 输入用户名 | testuser | | |\n| 输入密码 | Test@123 | | |\n| 点击登录 | | | |\n| 验证跳转 | /home | | |"},{"language":"text","snippet":"优点：\n├─ 测试数据与逻辑分离\n├─ 易于添加新用例\n├─ 覆盖多种场景\n└─ 便于维护\n\n示例：\n@pytest.mark.parametrize(\"username,password,expected\", [\n (\"user1\", \"pass1\", \"success\"),\n (\"user2\", \"pass2\", \"success\"),\n (\"\", \"pass3\", \"error\"),\n (\"user4\", \"\", \"error\"),\n])\ndef test_login(username, password, expected):\n result = login(username, password)\n assert result == expected"},{"language":"text","snippet":"职责：\n├─ 测试范围：函数、类、模块\n├─ 执行速度：毫秒级\n├─ 维护成本：低\n└─ 覆盖目标：核心逻辑\n\n技术选型：\n├─ Java：JUnit 5 + Mockito\n├─ Python：Pytest + Mock\n├─ JavaScript：Jest + Sinon\n└─ Go：testing + testify\n\n最佳实践：\n├─ 测试与代码同步维护\n├─ 每个测试单一职责\n├─ 使用Mock隔离依赖\n├─ 测试命名清晰（Given-When-Then）\n└─ 保持测试快速（<100ms）"},{"language":"text","snippet":"职责：\n├─ 测试范围：接口、服务间交互\n├─ 执行速度：秒级\n├─ 维护成本：中\n└─ 覆盖目标：业务流程\n\n技术选型：\n├─ API测试：Postman/Newman/REST Assured\n├─ 数据库测试：TestContainers\n├─ 消息队列测试：Embedded Kafka\n└─ 服务虚拟化：WireMock/Mountebank\n\n最佳实践：\n├─ 使用真实依赖（TestContainers）\n├─ 测试数据可构造、可清理\n├─ 验证接口契约\n├─ 覆盖正常/异常/边界场景\n└─ 保持测试独立性"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: qa-test-automation-arch\ndescription: >-\n 当需要设计自动化测试框架、或者现有框架维护成本太高需要重构时使用此技能。运用 PageObject、分层测试、关键字驱动、数据驱动等模式设计可维护可扩展的自动化架构。不要直接写测试代码——先设计架构：选型（UI/API/单元）、分层（测试层/业务层/基础设施层）、数据管理（测试数据与脚本分离）和 CI 集成方案。好的自动化架构应该让写用例的人不需要懂底层实现。 触发场景：自动化架构、框架设计、自动化策略、自动化框架、测试框架架构、自动化维护困难需要重构时。 Use when the user asks about: test automation architecture — Page Object, layered test design, keyword-driven and data-driven frameworks, and data management.\nlicense: MIT\nallowed-tools: Read Grep Glob Bash\nmetadata:\n display-name: \"Test Automation Arch\"\n version: \"1.8.0\"\n when-to-use: \"用户说\\\"自动化架构\\\"、\\\"框架设计\\\"、\\\"自动化策略\\\"、\\\"自动化框架\\\"、\\\"测试框架架构\\\"、需要设计测试自动化架构、自动化维护困难需要重构时\"\n related-skills: \"{\\\"upstream\\\":[\\\"qa-tech-selection\\\",\\\"qa-test-strategy-design\\\"],\\\"downstream\\\":[\\\"qa-ci-cd-testing\\\",\\\"qa-api-testing\\\",\\\"qa-mobile-testing\\\",\\\"qa-tech-debt-management\\\"]}\"\n references: \"[\\\"references/layered-architecture.md\\\"]\"\n input-format: \"{\\\"required\\\":[{\\\"name\\\":\\\"测试策略\\\",\\\"type\\\":\\\"object\\\",\\\"description\\\":\\\"来自qa-test-strategy-design的测试策略\\\"},{\\\"name\\\":\\\"技术选型\\\",\\\"type\\\":\\\"object\\\",\\\"description\\\":\\\"来自qa-tech-selection的技术选型建议\\\"}],\\\"optional\\\":[{\\\"name\\\":\\\"项目约束\\\",\\\"type\\\":\\\"string\\\",\\\"description\\\":\\\"技术栈和团队限制\\\"}]}\"\n output-format: \"{\\\"traceability\\\":[\\\"每份架构设计带唯一ID（ARCH-XXXX）\\\"],\\\"structure\\\":[\\\"覆盖率：标注口径（基于现有需求/输入文档），禁止\\\\\\\"全覆盖/100%\\\\\\\"绝对化表述；缺失模块标注\\\\\\\"未覆盖+原因\\\\\\\"\\\",{\\\"automation_architecture\\\":\\\"自动化测试架构设计\\\"},{\\\"framework_selection\\\":\\\"框架选择建议\\\"},{\\\"layer_design\\\":\\\"分层设计\\\"},{\\\"maintenance_strategy\\\":\\\"维护策略\\\"}]}\"\n error-recovery-guidance: \"{\\\"on_failure\\\":\\\"自动化架构遗漏维护策略时回退到技术选型补充\\\",\\\"retry_behavior\\\":\\\"补充选型后重新设计架构\\\"}\"\n categories: \"[\\\"Development\\\",\\\"Testing\\\",\\\"DevOps\\\"]\"\n depth-requirement: \"{\\\"reference_value\\\":\\\"根据架构复杂度调整设计深度：简单×1/中等×2/复杂×3\\\",\\\"minimum\\\":\\\"至少覆盖层架构、工具集成、维护策略3个核心要素\\\"}\"\n---\n> ⚠️ 本技能单独使用效果有限，建议配合完整技能集（12 步工作流）使用。安装：npx skills add Kokxi/qa-test-skills\n\n> **⚠️ 安全警告**：本技能的示例可能涉及订单号、支付金额、截图、身份证、手机号等敏感数据。\n> 实际使用时请勿粘贴真实生产数据、客户信息或财务凭证；测试前应脱敏/掩码处理。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 测试自动化架构设计\n\n## 核心原则\n\n好的自动化架构——分层清晰、职责单一、易于维护、快速反馈。\n\n## 测试自动化金字塔\n\n> 📌 本节与 qa-test-strategy-design「测试金字塔」概念对应，但分层名称和比例不同——本技能侧重自动化落地（集成测试层名、70/20/10 比例），strategy-design 侧重策略规划（接口测试层名、60/30/10 比例）。修改时请确认两处含义，避免矛盾。\n\n```text\n ┌─────────────┐\n │ E2E测试 │ 10%\n │ (UI/API) │\n ├─────────────┤\n │ 集成测试 │ 20%\n │ (接口/服务) │\n ├─────────────┤\n │ 单元测试 │ 70%\n │ (函数/类) │\n └─────────────┘\n```\n\n## 加载时机\n\n| 什么时候读 | 读哪个 |\n|-----------|--------|\n| 设计自动化框架分层时 | [`references/layered-architecture.md`](references/layered-architecture.md) |\n\n> `分层架构设计`的完整内容已下沉至 `references/layered-architecture.md`，避免每次触发都占用上下文。\n\n## 框架设计模式\n\n### Page Object Model\n\n```text\n优点：\n├─ 封装页面元素和操作\n├─ 减少代码重复\n├─ 易于维护\n└─ 可读性强\n\n示例结构：\ntests/\n├── pages/\n│ ├── login_page.py\n│ ├── home_page.py\n│ └── cart_page.py\n├── tests/\n│ ├── test"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n \"slug\": \"qa-test-automation-arch\",\n \"version\": \"1.8.0\",\n \"publishedAt\": 1790656146140\n}"},{"path":"references/layered-architecture.md","content":"# 测试分层架构设计详解\n\n> 本文是 `qa-test-automation-arch` 的**测试分层架构设计详解**。设计自动化框架分层时读本文；\n其余部分留在 SKILL.md，不必读本文。\n\n---\n\n\n### 第1层：单元测试层\n\n```text\n职责：\n├─ 测试范围：函数、类、模块\n├─ 执行速度：毫秒级\n├─ 维护成本：低\n└─ 覆盖目标：核心逻辑\n\n技术选型：\n├─ Java：JUnit 5 + Mockito\n├─ Python：Pytest + Mock\n├─ JavaScript：Jest + Sinon\n└─ Go：testing + testify\n\n最佳实践：\n├─ 测试与代码同步维护\n├─ 每个测试单一职责\n├─ 使用Mock隔离依赖\n├─ 测试命名清晰（Given-When-Then）\n└─ 保持测试快速（<100ms）\n```\n\n### 第2层：集成测试层\n\n```text\n职责：\n├─ 测试范围：接口、服务间交互\n├─ 执行速度：秒级\n├─ 维护成本：中\n└─ 覆盖目标：业务流程\n\n技术选型：\n├─ API测试：Postman/Newman/REST Assured\n├─ 数据库测试：TestContainers\n├─ 消息队列测试：Embedded Kafka\n└─ 服务虚拟化：WireMock/Mountebank\n\n最佳实践：\n├─ 使用真实依赖（TestContainers）\n├─ 测试数据可构造、可清理\n├─ 验证接口契约\n├─ 覆盖正常/异常/边界场景\n└─ 保持测试独立性\n```\n\n### 第3层：E2E测试层\n\n```text\n职责：\n├─ 测试范围：完整用户流程\n├─ 执行速度：分钟级\n├─ 维护成本：高\n└─ 覆盖目标：核心路径\n\n技术选型：\n├─ Web UI：Playwright/Cypress/Selenium\n├─ 移动端：Appium/XCUITest/Espresso\n├─ 桌面端：Electron Test/WinAppDriver\n└─ 性能：JMeter/Locust/k6\n\n最佳实践：\n├─ 只覆盖核心路径（20%）\n├─ 使用Page Object模式\n├─ 数据驱动测试\n├─ 稳定的等待策略\n└─ 失败时自动截图/录屏\n```"},{"path":"skill-card.md","content":"## Description:\n\nHelps QA engineers design maintainable test automation architectures with layered tests, framework selection, data management, and CI integration.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nQA engineers and developers use this skill to plan or refactor automated testing frameworks before writing tests. It guides test-layer design, framework selection, test-data separation, maintenance, and CI integration.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The suggested unpinned installation command may fetch an unreviewed release.\n\nMitigation: Review its source and pin a vetted version before running the command.\n\nRisk: Real customer, identity, payment, or screenshot data may be exposed when supplied to the workflow.\n\nMitigation: Use synthetic test data or mask sensitive information before sharing inputs.\n\n## Reference(s):\n\n- [Layered test architecture](references/layered-architecture.md)\n- [ClawHub skill release](https://clawhub.ai/kokxi/skills/qa-test-automation-arch)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Markdown]\n\n**Output Format:** [Markdown architecture plan]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Architecture ID (ARCH-XXXX); framework selection, layered design, and maintenance strategy; coverage claims scoped to supplied requirements.]\n\n## Skill Version(s):\n\n1.8.0 (source: skill frontmatter and server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"当需要设计自动化测试框架、或者现有框架维护成本太高需要重构时使用此技能。运用 PageObject、分层测试、关键字驱动、数据驱动等模式设计可维护可扩展的自动化架构。不要直接写测试代码——先设计架构：选型（UI/API/单元）、分层（测试层/业务层/基础设施层）、数据管理（测试数据与脚本分离）和 CI 集成方案。好的自动化架构应该让写用例的人不需要懂底层实现。 触发场景：自动化架构、框架设计、自动化策略、自动化框架、测试框架架构、自动化维护困难需要重构时。 Use when the user asks about: test automation architecture — Page Object, layered test design, keyword-driven and data-driven frameworks, and data management. Skill: qa-test-automation-arch Owner: kokxi Summary: 当需要设计自动化测试框架、或者现有框架维护成本太高需要重构时使用此技能。运用 PageObject、分层测试、关键字驱动、数据驱动等模式设计可维护可扩展的自动化架构。不要直接写测试代码——先设计架构：选型（UI/API/单元）、分层（测试层/业务层/基础设施层）、数据管理（测试数据与脚本分离）和 CI 集成方案。好的自动化架构应该让写用例的人不需要懂底层实现。 触发场景：自动化架构、框架设计、自动化策略、自动化框架、测试框架架构、自动化维护困难需要重构时。 Use when the user asks about: test automation architecture — Page Object, layered test design, keyword-driven and data-driven frameworks","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1014,"uniquenessScore":50,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T03:09:25.017Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T03:09:25.017Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T05:32:27.538Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}