test-planning

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Test Planning

测试计划

Create comprehensive test plans considering all test types, dependencies, risks, and project constraints to ensure effective quality assurance.

创建涵盖所有测试类型、依赖项、风险和项目约束的全面测试计划，以确保有效的质量保障。

When to use me

什么时候使用本技能

Use this skill when:

Starting new projects or major features
Planning testing strategy for releases
Allocating testing resources and timelines
Defining quality gates and acceptance criteria
Coordinating testing across teams or systems
Balancing test coverage with project constraints
Documenting testing approach for stakeholders

当出现以下场景时可使用本技能：

启动新项目或重大功能开发
为版本发布规划测试策略
分配测试资源和时间线
定义质量门禁和验收标准
跨团队或跨系统协调测试工作
在项目约束下平衡测试覆盖率
为利益相关者记录测试方案

What I do

我可以提供的服务

Test strategy development:
- Analyze project requirements and risks
- Select appropriate test types based on context
- Define test objectives and success criteria
- Establish quality gates and metrics
Resource planning:
- Estimate testing effort and timeline
- Allocate human and technical resources
- Plan test environment requirements
- Schedule test execution phases
Risk-based planning:
- Identify high-risk areas requiring focused testing
- Prioritize test coverage based on impact and likelihood
- Plan exploratory testing for unknown risks
- Design contingency plans for test failures
Integration planning:
- Coordinate with development and deployment schedules
- Plan test data management and environment setup
- Schedule test execution in CI/CD pipelines
- Coordinate with other teams and stakeholders

测试策略制定：
- 分析项目需求和风险
- 根据上下文选择合适的测试类型
- 定义测试目标和成功标准
- 建立质量门禁和度量指标
资源规划：
- 评估测试工作量和时间周期
- 分配人力和技术资源
- 规划测试环境需求
- 安排测试执行阶段
基于风险的规划：
- 识别需要重点测试的高风险领域
- 根据影响范围和发生概率优先级安排测试覆盖
- 为未知风险规划探索性测试
- 为测试失败设计应急预案
集成规划：
- 与开发和部署日程协调对齐
- 规划测试数据管理和环境搭建
- 在CI/CD流水线中安排测试执行
- 与其他团队和利益相关者协调

Test Planning Components

测试计划组成部分

Test Objectives: What are we trying to achieve?
Test Scope: What's included and excluded?
Test Approach: How will testing be conducted?
Test Schedule: When will testing happen?
Resources: Who and what is needed?
Deliverables: What will be produced?
Risks and Mitigations: What could go wrong?

测试目标：我们需要达成什么目标？
测试范围：包含和不包含哪些内容？
测试方案：如何开展测试？
测试日程：测试在什么时候进行？
资源：需要哪些人员和物资？
交付物：会产出哪些内容？
风险和缓解措施：可能会出现什么问题？

Examples

示例

bash

undefined

bash

undefined

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

undefined

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

undefined

Output format

输出格式

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

全面测试计划
──────────────────────────────
项目：电商平台 v2.1
阶段：Beta → 正式发布
规划日期：2024-03-15

测试目标：
  - 验证新结账流程功能
  - 确保与现有功能的向后兼容性
  - 满足峰值流量下的性能SLA
  - 维持安全合规性（PCI-DSS）
  - 为正式发布提供可信度支撑

测试范围：
  包含：
    - 新结账API和UI
    - 支付网关集成更新
    - 订单处理能力增强
    - 用户通知系统
  
  不包含：
    -  Legacy管理面板（单独版本发布）
    - 移动应用更新（其他团队负责）
    - 第三方分析集成

测试方案：
  测试金字塔落地：
    - 单元测试：新代码覆盖率达80%（预计：250条测试用例）
    - 集成测试：API和数据库集成（预计：75条测试用例）
    - E2E测试：核心用户路径（预计：25个场景）
  
  专项测试：
    - 性能测试：2000并发用户负载测试
    - 安全测试：PCI-DSS合规性验证
    - 可访问性测试：符合WCAG 2.1 AA标准
    - 兼容性测试：Chrome、Firefox、Safari、移动浏览器

测试日程：
  第1-2周：开发与单元测试
  第3周：集成测试与API验证
  第4周：E2E测试与用户验收
  第5周：性能与安全测试
  第6周：最终验证与生产就绪检查

资源分配：
  - 开发人员：3名（负责单元和集成测试）
  - QA工程师：2名（负责E2E和探索性测试）
  - 性能工程师：1名（负责负载测试）
  - 安全专家：1名（负责合规性验证）
  - 环境：开发环境、CI环境、预发环境、性能实验室

测试环境要求：
  - 与生产配置一致的预发环境
  - 具备类生产数据量级的测试数据库
  - 支付网关沙箱账号
  - 负载测试基础设施
  - 安全扫描工具

质量门禁：
  1. 所有单元测试通过（CI门禁）
  2. 集成测试100%通过（CI门禁）
  3. E2E核心路径100%通过（预发环境门禁）
  4. 满足性能SLA要求（性能门禁）
  5. 无高危安全漏洞（安全门禁）
  6. 用户验收签字通过（UAT门禁）

风险评估：
  高风险：
    - 支付处理集成（缓解措施：延长沙箱测试时间）
    - 数据库迁移（缓解措施：回滚测试）
  
  中风险：
    - 结账UI变更（缓解措施：全面E2E测试）
    - 负载下性能表现（缓解措施：渐进式负载测试）
  
  低风险：
    - 通知系统更新（缓解措施：冒烟测试）

依赖项：
  - 第2周前完成开发工作
  - 预发环境可用
  - 测试数据准备完成
  - 第三方服务沙箱访问权限
  - 性能测试窗口（非高峰时段）

成功度量指标：
  - 缺陷检测率 > 90%
  - 测试自动化覆盖率 > 70%
  - 缺陷平均解决时长 < 8小时
  - 上线首周无严重缺陷

应急预案：
  - 日程缓冲：预留1周应对突发问题
  - 回滚流程已编写完成并经过测试
  - 提供功能开关支持灰度发布
  - 正式发布的监控方案

交付物：
  - 测试策略文档
  - 测试用例和自动化脚本
  - 测试执行报告
  - 缺陷追踪和解决记录
  - 发布就绪评估报告
  - 经验总结文档

Notes

注意事项

Test plans should be living documents, updated as needed
Involve stakeholders in test planning process
Balance comprehensive planning with agility
Consider both functional and non-functional requirements
Document assumptions and constraints explicitly
Align test planning with business objectives
Use historical data to improve planning accuracy
Communicate test plan clearly to all involved parties
Review and adjust plans based on actual progress
Capture lessons learned for future planning improvements

测试计划应为活文档，可根据需要更新
测试规划过程需要利益相关者参与
在全面规划和敏捷性之间做好平衡
同时考虑功能和非功能需求
明确记录假设和约束条件
测试规划与业务目标对齐
利用历史数据提升规划准确性
向所有参与方清晰传达测试计划
根据实际进度审核和调整计划
总结经验教训为未来规划优化提供参考