@zeyue0329/xiaoma-cli 1.0.49 → 6.0.0-alpha.13

package/xiaoma-core/tasks/project-integration-testing.md

@@ -1,477 +0,0 @@
-# Project Integration Testing - 项目集成测试
-
-## Task Overview
-
-**任务名称**: 项目集成测试  
-**任务ID**: project-integration-testing  
-**分类**: 质量保证与集成验证  
-**复杂度**: ⭐⭐⭐⭐⭐
-
-## Task Description
-
-当所有用户故事开发完成后，执行项目级别的综合集成测试，包括跨模块集成测试、端到端业务流程验证、性能测试、安全测试，确保整个系统的完整性和可交付性。
-
-## Input Requirements
-
-### 必需输入
-
-1. **所有已完成的用户故事**
-   - 状态为 "Done" 的用户故事
-   - 包含完整的实现代码和单元测试
-
-2. **系统集成配置** (integration_config.yaml)
-   - 各模块接口定义
-   - 集成测试环境配置
-
-3. **业务流程定义** (business_processes.yaml)
-   - 端到端业务流程规范
-   - 用户旅程定义
-
-### 可选输入
-
-1. **性能基准** (performance_benchmarks.yaml)
-   - 性能要求和基准指标
-   - 负载测试配置
-
-2. **安全测试规范** (security_test_specs.yaml)
-   - 安全测试用例
-   - 漏洞扫描配置
-
-## Processing Steps
-
-### 第1步: 集成测试环境准备
-
-```yaml
-environment_preparation:
-  infrastructure_setup:
-    - database_deployment: 部署完整数据库实例
-    - service_deployment: 部署所有微服务
-    - middleware_configuration: 配置中间件(Redis, MQ等)
-    - monitoring_setup: 设置监控和日志系统
-
-  data_preparation:
-    - test_data_generation: 生成测试数据集
-    - reference_data_loading: 加载参考数据
-    - user_account_setup: 设置测试用户账户
-    - permission_configuration: 配置权限和角色
-
-  configuration_validation:
-    - service_connectivity_check: 服务连接性检查
-    - database_schema_validation: 数据库结构验证
-    - api_endpoint_accessibility: API端点可访问性
-    - authentication_validation: 认证系统验证
-```
-
-### 第2步: 跨模块集成测试
-
-```yaml
-cross_module_integration:
-  api_integration_testing:
-    test_categories:
-      - service_to_service_communication: 服务间通信测试
-      - data_consistency_across_services: 跨服务数据一致性
-      - transaction_boundary_testing: 事务边界测试
-      - error_propagation_testing: 错误传播测试
-
-    test_scenarios:
-      user_management_integration:
-        - user_registration_to_profile_creation: 用户注册到个人资料创建
-        - authentication_to_authorization: 认证到授权流程
-        - user_data_synchronization: 用户数据同步
-
-      data_flow_integration:
-        - data_creation_to_storage: 数据创建到存储
-        - data_query_across_modules: 跨模块数据查询
-        - data_update_propagation: 数据更新传播
-
-      business_process_integration:
-        - workflow_execution: 工作流执行
-        - business_rule_enforcement: 业务规则执行
-        - state_transition_management: 状态转换管理
-```
-
-### 第3步: 端到端业务流程测试
-
-```yaml
-end_to_end_testing:
-  user_journey_testing:
-    complete_user_workflows:
-      - new_user_onboarding: 新用户入职完整流程
-      - core_business_operations: 核心业务操作流程
-      - user_account_management: 用户账户管理流程
-      - data_lifecycle_management: 数据生命周期管理
-
-    test_execution_approach:
-      - automated_ui_testing: 自动化UI测试
-      - api_sequence_testing: API序列测试
-      - database_state_validation: 数据库状态验证
-      - business_outcome_verification: 业务结果验证
-
-  business_scenario_validation:
-    critical_business_flows:
-      - primary_user_scenarios: 主要用户场景
-      - exception_handling_flows: 异常处理流程
-      - edge_case_scenarios: 边界情况场景
-      - integration_failure_recovery: 集成故障恢复
-
-    validation_criteria:
-      - functional_correctness: 功能正确性
-      - data_integrity: 数据完整性
-      - business_rule_compliance: 业务规则合规性
-      - user_experience_quality: 用户体验质量
-```
-
-### 第4步: 性能集成测试
-
-```yaml
-performance_integration:
-  performance_test_types:
-    load_testing:
-      - baseline_load_testing: 基准负载测试
-      - peak_load_simulation: 峰值负载模拟
-      - sustained_load_testing: 持续负载测试
-
-    stress_testing:
-      - system_breaking_point: 系统断点测试
-      - resource_exhaustion_scenarios: 资源耗尽场景
-      - recovery_capability_testing: 恢复能力测试
-
-    scalability_testing:
-      - horizontal_scaling_validation: 水平扩展验证
-      - database_performance_scaling: 数据库性能扩展
-      - concurrent_user_scaling: 并发用户扩展
-
-  performance_metrics:
-    response_time_metrics:
-      - api_response_times: API响应时间
-      - database_query_performance: 数据库查询性能
-      - end_to_end_transaction_time: 端到端事务时间
-
-    throughput_metrics:
-      - requests_per_second: 每秒请求数
-      - transactions_per_minute: 每分钟事务数
-      - data_processing_throughput: 数据处理吞吐量
-
-    resource_utilization:
-      - cpu_utilization: CPU利用率
-      - memory_consumption: 内存消耗
-      - database_connection_usage: 数据库连接使用
-```
-
-### 第5步: 安全集成测试
-
-```yaml
-security_integration:
-  security_test_categories:
-    authentication_security:
-      - login_security_validation: 登录安全验证
-      - session_management_testing: 会话管理测试
-      - token_security_validation: 令牌安全验证
-      - multi_factor_authentication: 多因素认证测试
-
-    authorization_security:
-      - role_based_access_control: 基于角色的访问控制
-      - resource_permission_validation: 资源权限验证
-      - privilege_escalation_prevention: 权限升级防护
-
-    data_security:
-      - data_encryption_validation: 数据加密验证
-      - sensitive_data_protection: 敏感数据保护
-      - data_masking_verification: 数据脱敏验证
-      - audit_trail_completeness: 审计跟踪完整性
-
-    api_security:
-      - input_validation_testing: 输入验证测试
-      - sql_injection_prevention: SQL注入防护
-      - cross_site_scripting_protection: XSS防护
-      - api_rate_limiting: API频率限制
-
-  penetration_testing:
-    automated_vulnerability_scanning:
-      - dependency_vulnerability_check: 依赖漏洞检查
-      - configuration_security_scan: 配置安全扫描
-      - network_security_analysis: 网络安全分析
-
-    manual_security_testing:
-      - business_logic_security: 业务逻辑安全
-      - workflow_security_validation: 工作流安全验证
-      - data_flow_security_analysis: 数据流安全分析
-```
-
-### 第6步: 系统可靠性测试
-
-```yaml
-reliability_testing:
-  fault_tolerance_testing:
-    service_failure_scenarios:
-      - single_service_failure: 单一服务故障
-      - database_connection_failure: 数据库连接故障
-      - network_partition_scenarios: 网络分区场景
-      - external_service_unavailability: 外部服务不可用
-
-    recovery_testing:
-      - automatic_failover_validation: 自动故障转移验证
-      - data_recovery_procedures: 数据恢复程序
-      - service_restart_behavior: 服务重启行为
-      - system_state_consistency: 系统状态一致性
-
-  disaster_recovery_testing:
-    backup_and_restore:
-      - database_backup_validation: 数据库备份验证
-      - full_system_restore: 完整系统恢复
-      - incremental_backup_testing: 增量备份测试
-
-    business_continuity:
-      - minimal_service_operation: 最小服务运行
-      - degraded_mode_functionality: 降级模式功能
-      - recovery_time_objectives: 恢复时间目标
-```
-
-## Test Automation Framework
-
-### 自动化测试执行
-
-```yaml
-automation_framework:
-  test_execution_engine:
-    parallel_test_execution:
-      - test_suite_parallelization: 测试套件并行化
-      - resource_isolated_testing: 资源隔离测试
-      - concurrent_environment_management: 并发环境管理
-
-    test_data_management:
-      - dynamic_test_data_generation: 动态测试数据生成
-      - test_data_cleanup: 测试数据清理
-      - data_state_isolation: 数据状态隔离
-
-    result_aggregation:
-      - test_result_consolidation: 测试结果合并
-      - cross_test_correlation: 跨测试关联分析
-      - failure_root_cause_analysis: 故障根因分析
-
-  continuous_integration:
-    automated_triggers:
-      - story_completion_trigger: 故事完成触发
-      - dependency_satisfaction_trigger: 依赖满足触发
-      - scheduled_regression_testing: 定期回归测试
-
-    quality_gates:
-      - integration_test_pass_rate: 集成测试通过率(>95%)
-      - performance_benchmark_compliance: 性能基准合规性
-      - security_vulnerability_threshold: 安全漏洞阈值(零高危)
-```
-
-### 测试报告生成
-
-```yaml
-reporting_system:
-  comprehensive_test_reports:
-    executive_summary:
-      - overall_system_health: 整体系统健康度
-      - critical_issues_summary: 关键问题摘要
-      - recommendation_priorities: 建议优先级
-
-    detailed_analysis:
-      - module_integration_status: 模块集成状态
-      - performance_analysis_report: 性能分析报告
-      - security_assessment_report: 安全评估报告
-      - reliability_validation_report: 可靠性验证报告
-
-    actionable_insights:
-      - improvement_recommendations: 改进建议
-      - risk_mitigation_strategies: 风险缓解策略
-      - deployment_readiness_assessment: 部署就绪评估
-```
-
-## Quality Gates and Validation
-
-### 集成测试质量门控
-
-```yaml
-quality_gates:
-  functional_quality_gate:
-    criteria:
-      - integration_test_pass_rate: ≥98%
-      - end_to_end_scenario_success: 100%
-      - critical_business_flow_validation: 100%
-      - data_consistency_validation: 100%
-
-    validation_process:
-      - automated_test_execution: 自动化测试执行
-      - manual_validation_checkpoint: 人工验证检查点
-      - business_stakeholder_approval: 业务干系人审批
-
-  performance_quality_gate:
-    criteria:
-      - response_time_sla_compliance: 满足响应时间SLA
-      - throughput_benchmark_achievement: 达到吞吐量基准
-      - resource_utilization_efficiency: 资源利用率效率
-      - scalability_requirement_satisfaction: 满足扩展性要求
-
-  security_quality_gate:
-    criteria:
-      - zero_high_severity_vulnerabilities: 零高危漏洞
-      - authentication_security_validation: 认证安全验证通过
-      - data_protection_compliance: 数据保护合规性
-      - access_control_effectiveness: 访问控制有效性
-```
-
-### 交付就绪评估
-
-```yaml
-delivery_readiness:
-  technical_readiness:
-    code_quality_metrics:
-      - integration_test_coverage: ≥90%
-      - code_quality_score: ≥8.5/10
-      - technical_debt_ratio: ≤5%
-
-    system_stability:
-      - uptime_requirement: ≥99.5%
-      - error_rate_threshold: ≤0.1%
-      - recovery_time_objective: ≤15分钟
-
-  business_readiness:
-    functional_completeness:
-      - requirements_coverage: 100%
-      - acceptance_criteria_satisfaction: 100%
-      - user_journey_validation: 100%
-
-    operational_readiness:
-      - deployment_procedures: 已验证
-      - monitoring_systems: 已配置
-      - support_documentation: 已完成
-```
-
-## Output Generation
-
-### 集成测试报告
-
-```yaml
-# integration_test_report.yaml
-test_report:
-  executive_summary:
-    overall_status: "PASSED"
-    system_readiness: "READY_FOR_DEPLOYMENT"
-    critical_issues: 0
-    total_test_cases: 2847
-    pass_rate: 98.7%
-
-  module_integration_results:
-    user_management_module:
-      status: "PASSED"
-      test_cases: 456
-      pass_rate: 99.1%
-      critical_issues: 0
-
-    data_management_module:
-      status: "PASSED"
-      test_cases: 623
-      pass_rate: 98.9%
-      critical_issues: 0
-
-  performance_results:
-    load_testing:
-      baseline_load: "PASSED"
-      peak_load: "PASSED"
-      sustained_load: "PASSED"
-
-    response_time_analysis:
-      average_api_response: "245ms"
-      p95_response_time: "680ms"
-      p99_response_time: "1.2s"
-
-  security_assessment:
-    vulnerability_scan: "PASSED"
-    penetration_test: "PASSED"
-    compliance_check: "PASSED"
-    high_severity_issues: 0
-
-  recommendations:
-    - "优化数据库查询性能，减少p99响应时间"
-    - "增加API监控告警机制"
-    - "完善错误处理和用户友好提示"
-```
-
-### 交付清单
-
-```yaml
-# delivery_checklist.yaml
-delivery_package:
-  code_deliverables:
-    - source_code: "完整源代码包"
-    - build_artifacts: "构建产物"
-    - database_scripts: "数据库部署脚本"
-    - configuration_files: "配置文件模板"
-
-  documentation:
-    - api_documentation: "API接口文档"
-    - deployment_guide: "部署指南"
-    - user_manual: "用户使用手册"
-    - maintenance_guide: "维护运营指南"
-
-  test_artifacts:
-    - test_suites: "完整测试套件"
-    - test_data: "测试数据集"
-    - performance_benchmarks: "性能基准报告"
-    - security_audit_report: "安全审计报告"
-
-  operational_requirements:
-    - infrastructure_specifications: "基础设施规格"
-    - monitoring_configuration: "监控配置"
-    - backup_procedures: "备份程序"
-    - disaster_recovery_plan: "灾难恢复计划"
-```
-
-## Integration with Full Requirement Orchestrator
-
-### 集成点配置
-
-```yaml
-orchestrator_integration:
-  trigger_conditions:
-    all_stories_completed: "所有用户故事状态为Done"
-    individual_story_tests_passed: "所有故事单元测试通过"
-    dependency_integration_ready: "依赖集成就绪"
-
-  execution_command: "*execute-project-integration"
-
-  success_criteria:
-    integration_tests_passed: "集成测试100%通过"
-    performance_benchmarks_met: "性能基准达标"
-    security_validation_complete: "安全验证完成"
-
-  failure_handling:
-    rollback_strategy: "回滚到最后稳定版本"
-    issue_triage: "问题分级和分配"
-    remediation_planning: "修复计划制定"
-```
-
-## Usage Examples
-
-### 执行项目集成测试
-
-```bash
-# 在全需求编排器中执行
-*agent full-requirement-orchestrator
-*execute-project-integration
-
-# 查看集成测试状态
-*monitor-integration-progress
-
-# 生成交付报告
-*generate-project-deliverables
-```
-
-### 故障处理
-
-```bash
-# 处理集成测试失败
-*handle-integration-failure
-
-# 执行部分重测
-*retry-failed-integration-tests
-
-# 生成问题分析报告
-*analyze-integration-issues
-```

package/xiaoma-core/tasks/qa-gate.md

@@ -1,163 +0,0 @@
-<!-- Powered by XiaoMa™ Core -->
-
-# qa-gate
-
-Create or update a quality gate decision file for a story based on review findings.
-
-## Purpose
-
-Generate a standalone quality gate file that provides a clear pass/fail decision with actionable feedback. This gate serves as an advisory checkpoint for teams to understand quality status.
-
-## Prerequisites
-
-- Story has been reviewed (manually or via review-story task)
-- Review findings are available
-- Understanding of story requirements and implementation
-
-## Gate File Location
-
-**ALWAYS** check the `xiaoma-core/core-config.yaml` for the `qa.qaLocation/gates`
-
-Slug rules:
-
-- Convert to lowercase
-- Replace spaces with hyphens
-- Strip punctuation
-- Example: "User Auth - Login!" becomes "user-auth-login"
-
-## Minimal Required Schema
-
-```yaml
-schema: 1
-story: "{epic}.{story}"
-gate: PASS|CONCERNS|FAIL|WAIVED
-status_reason: "1-2 sentence explanation of gate decision"
-reviewer: "Quinn"
-updated: "{ISO-8601 timestamp}"
-top_issues: [] # Empty array if no issues
-waiver: { active: false } # Only set active: true if WAIVED
-```
-
-## Schema with Issues
-
-```yaml
-schema: 1
-story: "1.3"
-gate: CONCERNS
-status_reason: "Missing rate limiting on auth endpoints poses security risk."
-reviewer: "Quinn"
-updated: "2025-01-12T10:15:00Z"
-top_issues:
-  - id: "SEC-001"
-    severity: high # ONLY: low|medium|high
-    finding: "No rate limiting on login endpoint"
-    suggested_action: "Add rate limiting middleware before production"
-  - id: "TEST-001"
-    severity: medium
-    finding: "No integration tests for auth flow"
-    suggested_action: "Add integration test coverage"
-waiver: { active: false }
-```
-
-## Schema when Waived
-
-```yaml
-schema: 1
-story: "1.3"
-gate: WAIVED
-status_reason: "Known issues accepted for MVP release."
-reviewer: "Quinn"
-updated: "2025-01-12T10:15:00Z"
-top_issues:
-  - id: "PERF-001"
-    severity: low
-    finding: "Dashboard loads slowly with 1000+ items"
-    suggested_action: "Implement pagination in next sprint"
-waiver:
-  active: true
-  reason: "MVP release - performance optimization deferred"
-  approved_by: "Product Owner"
-```
-
-## Gate Decision Criteria
-
-### PASS
-
-- All acceptance criteria met
-- No high-severity issues
-- Test coverage meets project standards
-
-### CONCERNS
-
-- Non-blocking issues present
-- Should be tracked and scheduled
-- Can proceed with awareness
-
-### FAIL
-
-- Acceptance criteria not met
-- High-severity issues present
-- Recommend return to InProgress
-
-### WAIVED
-
-- Issues explicitly accepted
-- Requires approval and reason
-- Proceed despite known issues
-
-## Severity Scale
-
-**FIXED VALUES - NO VARIATIONS:**
-
-- `low`: Minor issues, cosmetic problems
-- `medium`: Should fix soon, not blocking
-- `high`: Critical issues, should block release
-
-## Issue ID Prefixes
-
-- `SEC-`: Security issues
-- `PERF-`: Performance issues
-- `REL-`: Reliability issues
-- `TEST-`: Testing gaps
-- `MNT-`: Maintainability concerns
-- `ARCH-`: Architecture issues
-- `DOC-`: Documentation gaps
-- `REQ-`: Requirements issues
-
-## Output Requirements
-
-1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `xiaoma-core/core-config.yaml`
-2. **ALWAYS** append this exact format to story's QA Results section:
-
-   ```text
-   Gate: {STATUS} → qa.qaLocation/gates/{epic}.{story}-{slug}.yml
-   ```
-
-3. Keep status_reason to 1-2 sentences maximum
-4. Use severity values exactly: `low`, `medium`, or `high`
-
-## Example Story Update
-
-After creating gate file, append to story's QA Results section:
-
-```markdown
-## QA Results
-
-### Review Date: 2025-01-12
-
-### Reviewed By: Quinn (Test Architect)
-
-[... existing review content ...]
-
-### Gate Status
-
-Gate: CONCERNS → qa.qaLocation/gates/{epic}.{story}-{slug}.yml
-```
-
-## Key Principles
-
-- Keep it minimal and predictable
-- Fixed severity scale (low/medium/high)
-- Always write to standard path
-- Always update story with gate reference
-- Clear, actionable findings