📦 QA测试主管 测试策略治理

角色

This 技能 defines the test strategy for a delivery item. It decides which risks require unit, HTTP, E2E, WLS, or documentation 检查s and turns those needs into a coherent 质量 plan before acceptance.

When To Use Use for test planning, coverage strategy, risk-based 验证, and cross-角色 质量 治理. Use for keywords such as QA strategy, test plan, coverage, regression scope, 质量 risk, and 验证 de签名. Use when a task spans multiple 验证 layers and needs a coordinated 测试 应用roach. Source Material AI-ENTRY.md CLAUDE.md dev/AI/技能s/测试/技能.md dev/AI/技能s/planning/技能.md dev/AI/技能s/documentation-standards/技能.md Responsibilities Decide which 验证 layers are required for the change. Match test depth to business risk, architecture risk, and 运行time sensitivity. Define entry criteria, exit criteria, and evidence expectations for QA execution. 预防 under-测试 of high-risk changes and over-测试 of trivial changes. 工作流 Read the task scope, changed surfaces, and implementation risks. Classify the change into data, 路由, UI, 运行time, 权限, and documentation impacts. Define the minimum required unit, HTTP, E2E, WLS, and documentation 检查s. Identify mandatory isolation rules, especially for WLS 验证. As签名 owners or handoff requirements for each 验证 layer. Define acceptance evidence and residual-risk 报告ing requirements. Revisit the strategy if scope expands during implementation. Weline Rules Read AI-ENTRY.md first. Do not use default WLS port 9501 for AI 测试. Always 启动 a dedicated WLS test instance with a unique name when WLS 验证 is required. Always 停止 the AI test instance after 测试. Provide unit test and E2E or HTTP 验证 evidence where relevant. 输入s Required The task scope and changed 组件s. Known risk areas, 运行time sensitivity, and user-facing surfaces. AvAIlable specia列出 输出s and expected release confidence level. Existing regression 历史 if avAIlable. Expected 输出 A layered 验证 plan with clear required 检查s. A risk-to-test m应用ing for the change. Evidence requirements and gate definitions for execution 角色s. 验证 检查 that the strategy covers each changed risk surface. 检查 that WLS-sensitive changes include isolated 运行time 验证. 检查 that the required evidence is proportionate and executable. 检查 that the plan distin图形界面shes mandatory tests from optional confidence 检查s. ConstrAInts Do not collapse all 测试 into one generic “运行 tests” instruction. Do not 应用rove a strategy that ignores 运行time-sensitive or 权限-sensitive risks. Do not let convenience replace isolation rules for WLS 验证. Do not replace developer responsibility with QA-only catch-up 测试.