Release Testing Workflow

发布测试工作流

中文版： 见技能

release-testing-workflow

。

End-to-end release testing (1–2 weeks before release through post-release). Prompts: see reference.md and this directory's prompts/
.

中文版： 见技能

release-testing-workflow

。

端到端发布测试（从发布前1-2周到发布后）。提示词：请查看reference.md及本目录下的**

prompts/

**文件夹。

When to Use

适用场景

User mentions release testing, Go/No-Go, or release readiness
Need timeline: T-14 planning → T-7 feature freeze → T-5–T-4 specialized testing → T-3 RC → T-2 quality assessment → T-1 Go/No-Go → T-day release → T+1–T+7 post-release
Trigger: e.g. “How do we schedule pre-release testing?” or “Go/No-Go checklist”

用户提及发布测试、Go/No-Go或发布就绪
需要明确时间线：T-14规划 → T-7功能冻结 → T-5至T-4专项测试 → T-3候选版本（RC）测试 → T-2质量评估 → T-1上线决策（Go/No-Go） → 发布日（T-day）部署 → T+1至T+7发布后监控
触发场景： 例如“我们如何安排发布前测试？”或“Go/No-Go检查清单”

How to Use the Prompts

提示词使用方法

For each step: 1) Check reference.md for the prompt file; 2) Open that file under this directory’s

prompts/

; 3) Combine the prompt with the current release context (scope, environment, gate criteria) and run with the AI.

对于每个步骤：1) 查看reference.md获取对应的提示词文件；2) 打开本目录下

prompts/

文件夹中的对应文件；3) 将提示词与当前发布的上下文信息（范围、环境、门禁标准）结合后，与AI配合使用。

Common Pitfalls

常见误区

❌ Adding features after T-7 → ✅ Feature freeze: only defect fixes; non-critical code freeze
❌ Releasing without Go/No-Go → ✅ Release only after gates pass, team alignment, and rollback readiness
❌ No post-release monitoring → ✅ T+1 intensive monitoring and fast response; follow incident procedures

❌ 在T-7之后添加新功能 → ✅ 执行功能冻结：仅允许缺陷修复；非关键代码冻结
❌ 未进行Go/No-Go决策就发布 → ✅ 仅在通过所有门禁标准、团队达成共识且回滚方案就绪后再发布
❌ 无发布后监控 → ✅ T+1阶段进行密集监控并快速响应；遵循事件处理流程

Best Practices

最佳实践

T-14: use test strategy and requirements prompts for release plan and risk assessment
T-2: use test reporting and test strategy for quality gates and known-issue assessment
Before deploy: confirm rollback tested, communication plan and support brief ready
Principle: When in doubt, delay release.

T-14阶段：使用测试策略和需求分析提示词制定发布计划并完成风险评估
T-2阶段：使用测试报告和测试策略提示词进行质量门禁检查和已知问题评估
部署前：确认回滚方案已测试、沟通计划和支持简报已准备就绪
原则： 存疑时，延迟发布。

Reference Files

参考文件

reference.md — Step-to-prompt file mapping
prompts/ — English prompt files for this workflow (open the matching
```
.md
```
per step and use with context)

Related: daily-testing-workflow-en, sprint-testing-workflow-en.

reference.md — 步骤与提示词文件的映射关系
prompts/ — 本工作流的英文提示词文件（根据步骤打开对应的
```
.md
```
文件并结合上下文使用）

相关内容： daily-testing-workflow-en, sprint-testing-workflow-en.

T-14: Release Planning

T-14：发布规划

☑️ Planning Meeting Checklist

☑️ 规划会议检查清单

Meeting preparation
- Confirm participants (Product, Engineering, QA, DevOps)
- Prepare meeting agenda
- Use prompts: test-strategy, requirements-analysis
Meeting agenda execution
- Define release scope
- Identify high-risk features
- Define quality gates
- Develop test strategy

☑️ Deliverables Completion Checklist

☑️ 交付物完成检查清单

T-10 to T-8: Test Preparation

T-10至T-8：测试准备

☑️ Environment Preparation Checklist

☑️ 环境准备检查清单

Test environment setup
- Set up pre-production environment
- Prepare production-like data
- Configure monitoring and logging
- Create test accounts
- Use prompts: automation-testing, test-strategy

☑️ Test Suite Update Checklist

☑️ 测试套件更新检查清单

☑️ Readiness Verification Checklist

☑️ 就绪状态验证检查清单

T-7: Feature Freeze & Testing Acceleration

T-7：功能冻结与测试加速

☑️ Feature Freeze Rules Confirmation

☑️ 功能冻结规则确认

Freeze rules enforcement
- Confirm no new features added
- Only allow defect fixes
- Non-critical code freeze

冻结规则执行
- 确认不再添加新功能
- 仅允许缺陷修复
- 非关键代码冻结

☑️ Functional Testing Checklist

☑️ 功能测试检查清单

☑️ Regression Testing Checklist

☑️ 回归测试检查清单

Full regression execution
- Execute full automated regression
- Execute critical path manual tests
- Cross-browser testing
- Mobile testing
- Use prompts: functional-testing, ai-assisted-testing

全量回归测试执行
- 执行全量自动化回归测试
- 执行关键路径手动测试
- 跨浏览器测试
- 移动端测试
- 使用提示词：functional-testing、ai-assisted-testing

☑️ End-to-End Testing Checklist

☑️ 端到端测试检查清单

T-5 to T-4: Specialized Testing

T-5至T-4：专项测试

☑️ Performance Testing Checklist

☑️ 性能测试检查清单

☑️ Security Testing Checklist

☑️ 安全测试检查清单

☑️ Accessibility Testing Checklist

☑️ 无障碍测试检查清单

☑️ Visual Testing Checklist

☑️ 视觉测试检查清单

T-3: Release Candidate (RC) Testing

T-3：候选版本（RC）测试

☑️ RC Deployment Checklist

☑️ RC部署检查清单

Release candidate preparation
- Deploy RC to pre-production
- Code freeze
- Tag version

候选版本准备
- 将RC部署到预生产环境
- 代码冻结
- 版本打标签

☑️ Smoke Testing Checklist

☑️ 冒烟测试检查清单

Quick smoke test (1–2 hours)
- Test critical features
- Confirm no critical defects
- Verify deployment success

快速冒烟测试（1-2小时）
- 测试关键功能
- 确认无严重缺陷
- 验证部署成功

☑️ Final Regression Checklist

☑️ 最终回归测试检查清单

Full regression execution
- Execute full automated regression
- Execute manual critical path tests
- Execute exploratory testing
- Use prompts: manual-testing

全量回归测试执行
- 执行全量自动化回归测试
- 执行手动关键路径测试
- 执行探索性测试
- 使用提示词：manual-testing

☑️ Defect Triage Checklist

☑️ 缺陷分级处理检查清单

Defect handling decisions
- Critical defects: must fix → retest → new RC
- High priority: assess risk
- Medium/low priority: move to next version

缺陷处理决策
- 严重缺陷：必须修复 → 重新测试 → 生成新的RC
- 高优先级缺陷：评估风险
- 中/低优先级缺陷：移至下一版本处理

T-2: Quality Assessment

T-2：质量评估

☑️ Quality Metrics Review Checklist

☑️ 质量指标评审检查清单

☑️ Quality Gate Check Checklist

☑️ 质量门禁检查清单

☑️ Risk Assessment Checklist

☑️ 风险评估检查清单

T-1: Go/No-Go

T-1：Go/No-Go（上线决策）

☑️ Go/No-Go Meeting Checklist

☑️ Go/No-Go会议检查清单

☑️ GO Decision Criteria Check

☑️ 上线（GO）决策标准检查

☑️ NO-GO Risk Identification

☑️ 不上线（NO-GO）风险识别

☑️ Pre-Release Checklist

☑️ 上线前检查清单

T-Day: Release Day

T-Day：发布日

☑️ Pre-Deployment Checklist (2–4 hours before)

☑️ 部署前检查清单（部署前2-4小时）

☑️ During Deployment Monitoring Checklist

☑️ 部署中监控检查清单

☑️ Post-Deployment Verification Checklist (30–60 min)

☑️ 部署后验证检查清单（30-60分钟）

☑️ First 24 Hours Monitoring Checklist

☑️ 首个24小时监控检查清单

☑️ Rollback Conditions Check

☑️ 回滚条件检查

Rollback trigger conditions
- Is critical functionality broken
- Is there severe performance degradation
- Is there data corruption
- Are there security vulnerabilities

release-testing-workflow-en

Original

Translation