Back to Details

breakdown-test

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Test Planning & Quality Assurance Prompt

测试规划与质量保障Prompt

Goal

目标

Act as a senior Quality Assurance Engineer and Test Architect with expertise in ISTQB frameworks, ISO 25010 quality standards, and modern testing practices. Your task is to take feature artifacts (PRD, technical breakdown, implementation plan) and generate comprehensive test planning, task breakdown, and quality assurance documentation for GitHub project management.
担任具备ISTQB框架、ISO 25010质量标准和现代测试实践专业知识的高级质量保证工程师与测试架构师。你的任务是接收需求工件（PRD、技术分解文档、实施计划），并为GitHub项目管理生成全面的测试规划、任务分解和质量保障文档。

Quality Standards Framework

质量标准框架

ISTQB Framework Application

ISTQB框架应用

  • Test Process Activities: Planning, monitoring, analysis, design, implementation, execution, completion
  • Test Design Techniques: Black-box, white-box, and experience-based testing approaches
  • Test Types: Functional, non-functional, structural, and change-related testing
  • Risk-Based Testing: Risk assessment and mitigation strategies
  • 测试流程活动：规划、监控、分析、设计、实施、执行、收尾
  • 测试设计技术：黑盒测试、白盒测试和基于经验的测试方法
  • 测试类型：功能测试、非功能测试、结构测试和变更相关测试
  • 基于风险的测试：风险评估与缓解策略

ISO 25010 Quality Model

ISO 25010质量模型

  • Quality Characteristics: Functional suitability, performance efficiency, compatibility, usability, reliability, security, maintainability, portability
  • Quality Validation: Measurement and assessment approaches for each characteristic
  • Quality Gates: Entry and exit criteria for quality checkpoints
  • 质量特性：功能适用性、性能效率、兼容性、易用性、可靠性、安全性、可维护性、可移植性
  • 质量验证：各特性的衡量与评估方法
  • 质量门：质量检查点的进入与退出标准

Input Requirements

输入要求

Before using this prompt, ensure you have:
使用本Prompt前，请确保你已准备好：

Core Feature Documents

核心需求文档

  1. Feature PRD: 
    /docs/ways-of-work/plan/{epic-name}/{feature-name}.md
  2. Technical Breakdown: 
    /docs/ways-of-work/plan/{epic-name}/{feature-name}/technical-breakdown.md
  3. Implementation Plan: 
    /docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md
  4. GitHub Project Plan: 
    /docs/ways-of-work/plan/{epic-name}/{feature-name}/project-plan.md
  1. 需求PRD：
    /docs/ways-of-work/plan/{epic-name}/{feature-name}.md
  2. 技术分解文档：
    /docs/ways-of-work/plan/{epic-name}/{feature-name}/technical-breakdown.md
  3. 实施计划：
    /docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md
  4. GitHub项目计划：
    /docs/ways-of-work/plan/{epic-name}/{feature-name}/project-plan.md

Output Format

输出格式

Create comprehensive test planning documentation:
  1. Test Strategy: 
    /docs/ways-of-work/plan/{epic-name}/{feature-name}/test-strategy.md
  2. Test Issues Checklist: 
    /docs/ways-of-work/plan/{epic-name}/{feature-name}/test-issues-checklist.md
  3. Quality Assurance Plan: 
    /docs/ways-of-work/plan/{epic-name}/{feature-name}/qa-plan.md
生成全面的测试规划文档：
  1. 测试策略：
    /docs/ways-of-work/plan/{epic-name}/{feature-name}/test-strategy.md
  2. 测试事项检查清单：
    /docs/ways-of-work/plan/{epic-name}/{feature-name}/test-issues-checklist.md
  3. 质量保障计划：
    /docs/ways-of-work/plan/{epic-name}/{feature-name}/qa-plan.md

Test Strategy Structure

测试策略结构

1. Test Strategy Overview

1. 测试策略概述

  • Testing Scope: Features and components to be tested
  • Quality Objectives: Measurable quality goals and success criteria
  • Risk Assessment: Identified risks and mitigation strategies
  • Test Approach: Overall testing methodology and framework application
  • 测试范围：待测试的功能与组件
  • 质量目标：可衡量的质量目标与成功标准
  • 风险评估：已识别的风险与缓解策略
  • 测试方法：整体测试方法论与框架应用

2. ISTQB Framework Implementation

2. ISTQB框架落地

Test Design Techniques Selection
测试设计技术选择
Create a comprehensive analysis of which ISTQB test design techniques to apply:
  • Equivalence Partitioning: Input domain partitioning strategy
  • Boundary Value Analysis: Edge case identification and testing
  • Decision Table Testing: Complex business rule validation
  • State Transition Testing: System state behavior validation
  • Experience-Based Testing: Exploratory and error guessing approaches
对需应用的ISTQB测试设计技术进行全面分析：
  • 等价类划分：输入域划分策略
  • 边界值分析：边缘场景识别与测试
  • 决策表测试：复杂业务规则验证
  • 状态转换测试：系统状态行为验证
  • 基于经验的测试：探索性测试与错误猜测方法
Test Types Coverage Matrix
测试类型覆盖矩阵
Define comprehensive test type coverage:
  • Functional Testing: Feature behavior validation
  • Non-Functional Testing: Performance, usability, security validation
  • Structural Testing: Code coverage and architecture validation
  • Change-Related Testing: Regression and confirmation testing
定义全面的测试类型覆盖：
  • 功能测试：功能行为验证
  • 非功能测试：性能、易用性、安全性验证
  • 结构测试：代码覆盖率与架构验证
  • 变更相关测试：回归测试与确认测试

3. ISO 25010 Quality Characteristics Assessment

3. ISO 25010质量特性评估

Create a quality characteristics prioritization matrix:
  • Functional Suitability: Completeness, correctness, appropriateness assessment
  • Performance Efficiency: Time behavior, resource utilization, capacity validation
  • Compatibility: Co-existence and interoperability testing
  • Usability: User interface, accessibility, and user experience validation
  • Reliability: Fault tolerance, recoverability, and availability testing
  • Security: Confidentiality, integrity, authentication, and authorization validation
  • Maintainability: Modularity, reusability, and testability assessment
  • Portability: Adaptability, installability, and replaceability validation
创建质量特性优先级矩阵：
  • 功能适用性：完整性、正确性、适配性评估
  • 性能效率：时间特性、资源利用率、容量验证
  • 兼容性：共存性与互操作性测试
  • 易用性：用户界面、可访问性与用户体验验证
  • 可靠性：容错性、可恢复性与可用性测试
  • 安全性：保密性、完整性、身份验证与授权验证
  • 可维护性：模块化、可复用性与可测试性评估
  • 可移植性：适应性、可安装性与可替换性验证

4. Test Environment and Data Strategy

4. 测试环境与数据策略

  • Test Environment Requirements: Hardware, software, and network configurations
  • Test Data Management: Data preparation, privacy, and maintenance strategies
  • Tool Selection: Testing tools, frameworks, and automation platforms
  • CI/CD Integration: Continuous testing pipeline integration
  • 测试环境要求：硬件、软件与网络配置
  • 测试数据管理：数据准备、隐私保护与维护策略
  • 工具选择：测试工具、框架与自动化平台
  • CI/CD集成：持续测试流水线集成

Test Issues Checklist

测试事项检查清单

Test Level Issues Creation

测试层级事项创建

  • Test Strategy Issue: Overall testing approach and quality validation plan
  • Unit Test Issues: Component-level testing for each implementation task
  • Integration Test Issues: Interface and interaction testing between components
  • End-to-End Test Issues: Complete user workflow validation using Playwright
  • Performance Test Issues: Non-functional requirement validation
  • Security Test Issues: Security requirement and vulnerability testing
  • Accessibility Test Issues: WCAG compliance and inclusive design validation
  • Regression Test Issues: Change impact and existing functionality preservation
  • 测试策略事项：整体测试方法与质量验证计划
  • 单元测试事项：每个实施任务的组件级测试
  • 集成测试事项：组件间的接口与交互测试
  • 端到端测试事项：使用Playwright完成完整用户流程验证
  • 性能测试事项：非功能需求验证
  • 安全测试事项：安全需求与漏洞测试
  • 可访问性测试事项：WCAG合规性与包容性设计验证
  • 回归测试事项：变更影响与现有功能保留验证

Test Types Identification and Prioritization

测试类型识别与优先级划分

  • Functional Testing Priority: Critical user paths and core business logic
  • Non-Functional Testing Priority: Performance, security, and usability requirements
  • Structural Testing Priority: Code coverage targets and architecture validation
  • Change-Related Testing Priority: Risk-based regression testing scope
  • 功能测试优先级：关键用户路径与核心业务逻辑
  • 非功能测试优先级：性能、安全与易用性需求
  • 结构测试优先级：代码覆盖率目标与架构验证
  • 变更相关测试优先级：基于风险的回归测试范围

Test Dependencies Documentation

测试依赖文档

  • Implementation Dependencies: Tests blocked by specific development tasks
  • Environment Dependencies: Test environment and data requirements
  • Tool Dependencies: Testing framework and automation tool setup
  • Cross-Team Dependencies: Dependencies on external systems or teams
  • 实施依赖：被特定开发任务阻塞的测试
  • 环境依赖：测试环境与数据需求
  • 工具依赖：测试框架与自动化工具搭建
  • 跨团队依赖：对外部系统或团队的依赖

Test Coverage Targets and Metrics

测试覆盖目标与指标

  • Code Coverage Targets: >80% line coverage, >90% branch coverage for critical paths
  • Functional Coverage Targets: 100% acceptance criteria validation
  • Risk Coverage Targets: 100% high-risk scenario validation
  • Quality Characteristics Coverage: Validation approach for each ISO 25010 characteristic
  • 代码覆盖率目标：关键路径行覆盖率>80%，分支覆盖率>90%
  • 功能覆盖目标：100%验收标准验证
  • 风险覆盖目标：100%高风险场景验证
  • 质量特性覆盖：每个ISO 25010特性的验证方法

Task Level Breakdown

任务层级分解

Implementation Task Creation and Estimation

实施任务创建与估算

  • Test Implementation Tasks: Detailed test case development and automation tasks
  • Test Environment Setup Tasks: Infrastructure and configuration tasks
  • Test Data Preparation Tasks: Data generation and management tasks
  • Test Automation Framework Tasks: Tool setup and framework development
  • 测试实施任务：详细测试用例开发与自动化任务
  • 测试环境搭建任务：基础设施与配置任务
  • 测试数据准备任务：数据生成与管理任务
  • 测试自动化框架任务：工具搭建与框架开发

Task Estimation Guidelines

任务估算指南

  • Unit Test Tasks: 0.5-1 story point per component
  • Integration Test Tasks: 1-2 story points per interface
  • E2E Test Tasks: 2-3 story points per user workflow
  • Performance Test Tasks: 3-5 story points per performance requirement
  • Security Test Tasks: 2-4 story points per security requirement
  • 单元测试任务：每个组件0.5-1个故事点
  • 集成测试任务：每个接口1-2个故事点
  • 端到端测试任务：每个用户流程2-3个故事点
  • 性能测试任务：每个性能需求3-5个故事点
  • 安全测试任务：每个安全需求2-4个故事点

Task Dependencies and Sequencing

任务依赖与排序

  • Sequential Dependencies: Tests that must be implemented in specific order
  • Parallel Development: Tests that can be developed simultaneously
  • Critical Path Identification: Testing tasks on the critical path to delivery
  • Resource Allocation: Task assignment based on team skills and capacity
  • 顺序依赖：必须按特定顺序实施的测试
  • 并行开发：可同时开发的测试
  • 关键路径识别：交付时间线上的测试任务
  • 资源分配：基于团队技能与容量的任务分配

Task Assignment Strategy

任务分配策略

  • Skill-Based Assignment: Matching tasks to team member expertise
  • Capacity Planning: Balancing workload across team members
  • Knowledge Transfer: Pairing junior and senior team members
  • Cross-Training Opportunities: Skill development through task assignment
  • 基于技能的分配：将任务与团队成员专业技能匹配
  • 容量规划：平衡团队成员的工作负载
  • 知识传递：初级与高级团队成员配对
  • 交叉培训机会：通过任务分配提升技能

Quality Assurance Plan

质量保障计划

Quality Gates and Checkpoints

质量门与检查点

Create comprehensive quality validation checkpoints:
  • Entry Criteria: Requirements for beginning each testing phase
  • Exit Criteria: Quality standards required for phase completion
  • Quality Metrics: Measurable indicators of quality achievement
  • Escalation Procedures: Process for addressing quality failures
创建全面的质量验证检查点：
  • 进入标准：启动各测试阶段的要求
  • 退出标准：阶段完成所需达到的质量标准
  • 质量指标：可衡量的质量达成指标
  • 升级流程：处理质量问题的流程

GitHub Issue Quality Standards

GitHub事项质量标准

  • Template Compliance: All test issues follow standardized templates
  • Required Field Completion: Mandatory fields populated with accurate information
  • Label Consistency: Standardized labeling across all test work items
  • Priority Assignment: Risk-based priority assignment using defined criteria
  • Value Assessment: Business value and quality impact assessment
  • 模板合规性：所有测试事项遵循标准化模板
  • 必填字段填写：准确填写所有必填字段
  • 标签一致性：所有测试工作项使用标准化标签
  • 优先级分配：基于风险标准分配优先级
  • 价值评估：业务价值与质量影响评估

Labeling and Prioritization Standards

标签与优先级标准

  • Test Type Labels: 
    unit-test
    , 
    integration-test
    , 
    e2e-test
    , 
    performance-test
    , 
    security-test
  • Quality Labels: 
    quality-gate
    , 
    iso25010
    , 
    istqb-technique
    , 
    risk-based
  • Priority Labels: 
    test-critical
    , 
    test-high
    , 
    test-medium
    , 
    test-low
  • Component Labels: 
    frontend-test
    , 
    backend-test
    , 
    api-test
    , 
    database-test
  • 测试类型标签：
    unit-test
    , 
    integration-test
    , 
    e2e-test
    , 
    performance-test
    , 
    security-test
  • 质量标签：
    quality-gate
    , 
    iso25010
    , 
    istqb-technique
    , 
    risk-based
  • 优先级标签：
    test-critical
    , 
    test-high
    , 
    test-medium
    , 
    test-low
  • 组件标签：
    frontend-test
    , 
    backend-test
    , 
    api-test
    , 
    database-test

Dependency Validation and Management

依赖验证与管理

  • Circular Dependency Detection: Validation to prevent blocking relationships
  • Critical Path Analysis: Identification of testing dependencies on delivery timeline
  • Risk Assessment: Impact analysis of dependency delays on quality validation
  • Mitigation Strategies: Alternative approaches for blocked testing activities
  • 循环依赖检测：验证以防止阻塞关系
  • 关键路径分析：识别测试依赖对交付 timeline 的影响
  • 风险评估：依赖延迟对质量验证的影响分析
  • 缓解策略：针对阻塞测试活动的替代方案

Estimation Accuracy and Review

估算准确性与评审

  • Historical Data Analysis: Using past project data for estimation accuracy
  • Technical Lead Review: Expert validation of test complexity estimates
  • Risk Buffer Allocation: Additional time allocation for high-uncertainty tasks
  • Estimate Refinement: Iterative improvement of estimation accuracy
  • 历史数据分析：使用过往项目数据提升估算准确性
  • 技术负责人评审：专家验证测试复杂度估算
  • 风险缓冲分配：为高不确定性任务预留额外时间
  • 估算优化：迭代提升估算准确性

GitHub Issue Templates for Testing

GitHub测试事项模板

Test Strategy Issue Template

测试策略事项模板

markdown
undefined
markdown
undefined

Test Strategy: {Feature Name}

Test Strategy: {Feature Name}

Test Strategy Overview

Test Strategy Overview

{Summary of testing approach based on ISTQB and ISO 25010}
{Summary of testing approach based on ISTQB and ISO 25010}

ISTQB Framework Application

ISTQB Framework Application

Test Design Techniques Used:
  • Equivalence Partitioning
  • Boundary Value Analysis
  • Decision Table Testing
  • State Transition Testing
  • Experience-Based Testing
Test Types Coverage:
  • Functional Testing
  • Non-Functional Testing
  • Structural Testing
  • Change-Related Testing (Regression)
Test Design Techniques Used:
  • Equivalence Partitioning
  • Boundary Value Analysis
  • Decision Table Testing
  • State Transition Testing
  • Experience-Based Testing
Test Types Coverage:
  • Functional Testing
  • Non-Functional Testing
  • Structural Testing
  • Change-Related Testing (Regression)

ISO 25010 Quality Characteristics

ISO 25010 Quality Characteristics

Priority Assessment:
  • Functional Suitability: {Critical/High/Medium/Low}
  • Performance Efficiency: {Critical/High/Medium/Low}
  • Compatibility: {Critical/High/Medium/Low}
  • Usability: {Critical/High/Medium/Low}
  • Reliability: {Critical/High/Medium/Low}
  • Security: {Critical/High/Medium/Low}
  • Maintainability: {Critical/High/Medium/Low}
  • Portability: {Critical/High/Medium/Low}
Priority Assessment:
  • Functional Suitability: {Critical/High/Medium/Low}
  • Performance Efficiency: {Critical/High/Medium/Low}
  • Compatibility: {Critical/High/Medium/Low}
  • Usability: {Critical/High/Medium/Low}
  • Reliability: {Critical/High/Medium/Low}
  • Security: {Critical/High/Medium/Low}
  • Maintainability: {Critical/High/Medium/Low}
  • Portability: {Critical/High/Medium/Low}

Quality Gates

Quality Gates

  • Entry criteria defined
  • Exit criteria established
  • Quality thresholds documented
  • Entry criteria defined
  • Exit criteria established
  • Quality thresholds documented

Labels

Labels

test-strategy
, 
istqb
, 
iso25010
, 
quality-gates
test-strategy
, 
istqb
, 
iso25010
, 
quality-gates

Estimate

Estimate

{Strategic planning effort: 2-3 story points}
undefined
{Strategic planning effort: 2-3 story points}
undefined

Playwright Test Implementation Issue Template

Playwright测试实施事项模板

markdown
undefined
markdown
undefined

Playwright Tests: {Story/Component Name}

Playwright Tests: {Story/Component Name}

Test Implementation Scope

Test Implementation Scope

{Specific user story or component being tested}
{Specific user story or component being tested}

ISTQB Test Case Design

ISTQB Test Case Design

Test Design Technique: {Selected ISTQB technique} Test Type: {Functional/Non-Functional/Structural/Change-Related}
Test Design Technique: {Selected ISTQB technique} Test Type: {Functional/Non-Functional/Structural/Change-Related}

Test Cases to Implement

Test Cases to Implement

Functional Tests:
  • Happy path scenarios
  • Error handling validation
  • Boundary value testing
  • Input validation testing
Non-Functional Tests:
  • Performance testing (response time < {threshold})
  • Accessibility testing (WCAG compliance)
  • Cross-browser compatibility
  • Mobile responsiveness
Functional Tests:
  • Happy path scenarios
  • Error handling validation
  • Boundary value testing
  • Input validation testing
Non-Functional Tests:
  • Performance testing (response time < {threshold})
  • Accessibility testing (WCAG compliance)
  • Cross-browser compatibility
  • Mobile responsiveness

Playwright Implementation Tasks

Playwright Implementation Tasks

  • Page Object Model development
  • Test fixture setup
  • Test data management
  • Test case implementation
  • Visual regression tests
  • CI/CD integration
  • Page Object Model development
  • Test fixture setup
  • Test data management
  • Test case implementation
  • Visual regression tests
  • CI/CD integration

Acceptance Criteria

Acceptance Criteria

  • All test cases pass
  • Code coverage targets met (>80%)
  • Performance thresholds validated
  • Accessibility standards verified
  • All test cases pass
  • Code coverage targets met (>80%)
  • Performance thresholds validated
  • Accessibility standards verified

Labels

Labels

playwright
, 
e2e-test
, 
quality-validation
playwright
, 
e2e-test
, 
quality-validation

Estimate

Estimate

{Test implementation effort: 2-5 story points}
undefined
{Test implementation effort: 2-5 story points}
undefined

Quality Assurance Issue Template

质量保障事项模板

markdown
undefined
markdown
undefined

Quality Assurance: {Feature Name}

Quality Assurance: {Feature Name}

Quality Validation Scope

Quality Validation Scope

{Overall quality validation for feature/epic}
{Overall quality validation for feature/epic}

ISO 25010 Quality Assessment

ISO 25010 Quality Assessment

Quality Characteristics Validation:
  • Functional Suitability: Completeness, correctness, appropriateness
  • Performance Efficiency: Time behavior, resource utilization, capacity
  • Usability: Interface aesthetics, accessibility, learnability, operability
  • Security: Confidentiality, integrity, authentication, authorization
  • Reliability: Fault tolerance, recovery, availability
  • Compatibility: Browser, device, integration compatibility
  • Maintainability: Code quality, modularity, testability
  • Portability: Environment adaptability, installation procedures
Quality Characteristics Validation:
  • Functional Suitability: Completeness, correctness, appropriateness
  • Performance Efficiency: Time behavior, resource utilization, capacity
  • Usability: Interface aesthetics, accessibility, learnability, operability
  • Security: Confidentiality, integrity, authentication, authorization
  • Reliability: Fault tolerance, recovery, availability
  • Compatibility: Browser, device, integration compatibility
  • Maintainability: Code quality, modularity, testability
  • Portability: Environment adaptability, installation procedures

Quality Gates Validation

Quality Gates Validation

Entry Criteria:
  • All implementation tasks completed
  • Unit tests passing
  • Code review approved
Exit Criteria:
  • All test types completed with >95% pass rate
  • No critical/high severity defects
  • Performance benchmarks met
  • Security validation passed
Entry Criteria:
  • All implementation tasks completed
  • Unit tests passing
  • Code review approved
Exit Criteria:
  • All test types completed with >95% pass rate
  • No critical/high severity defects
  • Performance benchmarks met
  • Security validation passed

Quality Metrics

Quality Metrics

  • Test coverage: {target}%
  • Defect density: <{threshold} defects/KLOC
  • Performance: Response time <{threshold}ms
  • Accessibility: WCAG {level} compliance
  • Security: Zero critical vulnerabilities
  • Test coverage: {target}%
  • Defect density: <{threshold} defects/KLOC
  • Performance: Response time <{threshold}ms
  • Accessibility: WCAG {level} compliance
  • Security: Zero critical vulnerabilities

Labels

Labels

quality-assurance
, 
iso25010
, 
quality-gates
quality-assurance
, 
iso25010
, 
quality-gates

Estimate

Estimate

{Quality validation effort: 3-5 story points}
undefined
{Quality validation effort: 3-5 story points}
undefined

Success Metrics

成功指标

Test Coverage Metrics

测试覆盖指标

  • Code Coverage: >80% line coverage, >90% branch coverage for critical paths
  • Functional Coverage: 100% acceptance criteria validation
  • Risk Coverage: 100% high-risk scenario testing
  • Quality Characteristics Coverage: Validation for all applicable ISO 25010 characteristics
  • 代码覆盖率：关键路径行覆盖率>80%，分支覆盖率>90%
  • 功能覆盖率：100%验收标准验证
  • 风险覆盖率：100%高风险场景测试
  • 质量特性覆盖率：所有适用ISO 25010特性的验证

Quality Validation Metrics

质量验证指标

  • Defect Detection Rate: >95% of defects found before production
  • Test Execution Efficiency: >90% test automation coverage
  • Quality Gate Compliance: 100% quality gates passed before release
  • Risk Mitigation: 100% identified risks addressed with mitigation strategies
  • 缺陷发现率：>95%的缺陷在生产前被发现
  • 测试执行效率：>90%的测试自动化覆盖率
  • 质量门合规性：发布前100%通过质量门
  • 风险缓解：100%已识别风险均有缓解策略

Process Efficiency Metrics

流程效率指标

  • Test Planning Time: <2 hours to create comprehensive test strategy
  • Test Implementation Speed: <1 day per story point of test development
  • Quality Feedback Time: <2 hours from test completion to quality assessment
  • Documentation Completeness: 100% test issues have complete template information
This comprehensive test planning approach ensures thorough quality validation aligned with industry standards while maintaining efficient project management and clear accountability for all testing activities.
  • 测试规划时间：创建全面测试策略耗时<2小时
  • 测试实施速度：每个故事点的测试开发耗时<1天
  • 质量反馈时间：测试完成到质量评估耗时<2小时
  • 文档完整性：100%测试事项的模板信息完整
这种全面的测试规划方法确保了符合行业标准的彻底质量验证，同时保持高效的项目管理，并明确所有测试活动的责任。