mcpField
T
test-planning

test-planning

github.com/wojons测试与质量338 次安装30 周前更新
代码仓库

关于 test-planning

test-planning 是用于制定项目、功能和版本 QA 计划的技能。它统筹测试范围、方法、日程、资源、依赖项与风险，并考虑项目约束。

主要功能

  1. 01分析需求与风险
  2. 02选择测试类型并定义目标
  3. 03估算工作量、时间线与资源
  4. 04规划环境和执行阶段
  5. 05协调团队及 CI/CD 测试
  6. 06设定质量门槛与成功标准

适用场景

  1. 01为新功能规划测试
  2. 02制定版本 QA 策略
  3. 03分配测试资源和时间
  4. 04为相关方记录验收标准

安装

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

$npx skills add https://github.com/wojons/skills --skill test-planning

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

包含的文件

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

README.md
references/
README.md
scripts/
example.sh

详细介绍

测试规划

制定全面的测试计划，考虑所有测试类型、依赖项、风险和项目约束，确保有效的质量保障。

何时使用我

在以下情况下使用此技能：

  • 启动新项目或重大功能
  • 规划发布的测试策略
  • 分配测试资源和时间
  • 定义质量门禁和验收标准
  • 协调跨团队或跨系统的测试
  • 在测试覆盖率与项目约束之间取得平衡
  • 为利益相关者记录测试方法

我能做什么

  • 测试策略制定：

    • 分析项目需求和风险
    • 根据具体情况选择合适的测试类型
    • 定义测试目标和成功标准
    • 建立质量门禁和指标

  • 资源规划：

    • 估算测试工作量和时间
    • 分配人力和技术资源
    • 规划测试环境需求
    • 安排各阶段的测试执行

  • 基于风险的规划：

    • 识别需要重点测试的高风险领域
    • 根据影响和发生可能性确定测试覆盖的优先级
    • 针对未知风险规划探索性测试
    • 为测试失败设计应急方案

  • 集成规划：

    • 协调开发和部署计划
    • 规划测试数据管理和环境设置
    • 安排在 CI/CD 流水线中执行测试
    • 与其他团队和利益相关者协调

测试规划要素

  1. 测试目标：我们要实现什么？
  2. 测试范围：包含和排除哪些内容？
  3. 测试方法：将如何开展测试？
  4. 测试计划：何时进行测试？
  5. 资源：需要哪些人员和资源？
  6. 交付物：将产出什么？
  7. 风险和缓解措施：可能出现什么问题？

示例

# Generate test plans
npm run test:plan:generate          # Generate comprehensive test plan
npm run test:plan:strategy          # Create test strategy document
npm run test:plan:estimate          # Estimate testing effort

# Feature-specific planning
npm run test:plan:feature -- "user-authentication"
npm run test:plan:release -- "v2.1.0"

# Context-aware planning
npm run test:plan -- --context mvp --type saas
npm run test:plan -- --context production --type enterprise

# Integration with project management
npm run test:plan:export -- --format jira    # Jira import format
npm run test:plan:export -- --format csv      # CSV for spreadsheets
npm run test:plan:export -- --format markdown # Markdown documentation

# Risk-based planning
npm run test:plan:risks            # Risk assessment and planning
npm run test:plan:coverage         # Test coverage planning

输出格式

Comprehensive Test Plan
──────────────────────────────
Project: E-Commerce Platform v2.1
Stage: Beta → Production Release
Planning Date: 2024-03-15

Test Objectives:
  - Validate new checkout flow functionality
  - Ensure backward compatibility with existing features
  - Meet performance SLAs for peak traffic
  - Maintain security compliance (PCI-DSS)
  - Provide confidence for production release

Test Scope:
  Included:
    - New checkout API and UI
    - Payment gateway integration updates
    - Order processing enhancements
    - User notification system
  
  Excluded:
    - Legacy admin panel (separate release)
    - Mobile app updates (different team)
    - Third-party analytics integration

Test Approach:
  Test Pyramid Implementation:
    - Unit Tests: 80% coverage on new code (estimated: 250 tests)
    - Integration Tests: API and database integration (estimated: 75 tests)
    - E2E Tests: Critical user journeys (estimated: 25 scenarios)
  
  Specialized Testing:
    - Performance: Load testing with 2000 concurrent users
    - Security: PCI-DSS compliance validation
    - Accessibility: WCAG 2.1 AA compliance
    - Compatibility: Chrome, Firefox, Safari, mobile browsers

Test Schedule:
  Week 1-2: Development & Unit Testing
  Week 3: Integration Testing & API Validation
  Week 4: E2E Testing & User Acceptance
  Week 5: Performance & Security Testing
  Week 6: Final Validation & Production Readiness

Resource Allocation:
  - Developers: 3 (unit & integration tests)
  - QA Engineers: 2 (E2E & exploratory testing)
  - Performance Engineer: 1 (load testing)
  - Security Specialist: 1 (compliance validation)
  - Environments: Dev, CI, Staging, Performance Lab

Test Environment Requirements:
  - Staging environment matching production configuration
  - Test database with production-like data volume
  - Payment gateway sandbox accounts
  - Load testing infrastructure
  - Security scanning tools

Quality Gates:
  1. All unit tests pass (CI gate)
  2. Integration tests 100% pass (CI gate)
  3. E2E critical paths 100% pass (staging gate)
  4. Performance SLAs met (performance gate)
  5. No critical security vulnerabilities (security gate)
  6. User acceptance sign-off (UAT gate)

Risk Assessment:
  High Risk:
    - Payment processing integration (mitigation: extended sandbox testing)
    - Database migration (mitigation: rollback testing)
  
  Medium Risk:
    - Checkout UI changes (mitigation: extensive E2E testing)
    - Performance under load (mitigation: progressive load testing)
  
  Low Risk:
    - Notification system updates (mitigation: smoke testing)

Dependencies:
  - Development completion by Week 2
  - Staging environment availability
  - Test data preparation
  - Third-party service sandbox access
  - Performance testing window (off-peak hours)

Success Metrics:
  - Defect detection rate > 90%
  - Test automation coverage > 70%
  - Mean time to defect resolution < 8 hours
  - Zero critical defects in production first week

Contingency Plans:
  - Schedule buffer: 1 week for unexpected issues
  - Rollback procedure documented and tested
  - Feature flags for gradual rollout
  - Monitoring plan for production release

Deliverables:
  - Test strategy document
  - Test cases and automation scripts
  - Test execution reports
  - Defect tracking and resolution
  - Release readiness assessment
  - Lessons learned document

注意事项

  • 测试计划应是持续更新的文档，并按需修订
  • 邀请利益相关者参与测试规划过程
  • 在全面规划与敏捷性之间取得平衡
  • 同时考虑功能性和非功能性需求
  • 明确记录假设和约束
  • 使测试规划与业务目标保持一致
  • 利用历史数据提高规划准确性
  • 向所有相关方清晰传达测试计划
  • 根据实际进度审查并调整计划
  • 总结经验教训，以改进未来的规划

评论

支持 Markdown