sprint-status.yaml 9.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198
  1. # generated: 2026-01-11
  2. # project: 188-179-template-6
  3. # project_key: 188-179-template-6
  4. # tracking_system: file-system
  5. # story_location: _bmad-output/implementation-artifacts
  6. # STATUS DEFINITIONS:
  7. # ==================
  8. # Epic Status:
  9. # - backlog: Epic not yet started
  10. # - in-progress: Epic actively being worked on
  11. # - done: All stories in epic completed
  12. #
  13. # Epic Status Transitions:
  14. # - backlog -> in-progress: Automatically when first story is created (via create-story)
  15. # - in-progress -> done: Manually when all stories reach 'done' status
  16. #
  17. # Story Status:
  18. # - backlog: Story only exists in epic file
  19. # - ready-for-dev: Story file created in stories folder
  20. # - in-progress: Developer actively working on implementation
  21. # - review: Ready for code review (via Dev's code-review workflow)
  22. # - done: Story completed
  23. #
  24. # Retrospective Status:
  25. # - optional: Can be completed but not required
  26. # - done: Retrospective has been completed
  27. #
  28. # WORKFLOW NOTES:
  29. # ===============
  30. # - Epic transitions to 'in-progress' automatically when first story is created
  31. # - Stories can be worked in parallel if team capacity allows
  32. # - SM typically creates next story after previous one is 'done' to incorporate learnings
  33. # - Dev moves story to 'review', then runs code-review (fresh context, different LLM recommended)
  34. generated: 2026-01-11T12:00:00Z
  35. project: 188-179-template-6
  36. project_key: 188-179-template-6
  37. tracking_system: file-system
  38. story_location: _bmad-output/implementation-artifacts
  39. development_status:
  40. # Epic 1: 测试工具包基础框架与 Select 支持
  41. epic-1: done
  42. 1-1-create-package-structure: done
  43. 1-2-implement-types-errors: done
  44. 1-3-static-select-tool: done
  45. 1-4-async-select-tool: done
  46. 1-5-main-export-docs: done
  47. 1-6-select-unit-tests: done
  48. epic-1-retrospective: done
  49. # Epic 2: 在现有 E2E 测试中验证 Select 工具
  50. # 详情参见: _bmad-output/implementation-artifacts/epic-2-retrospective.md
  51. epic-2: done
  52. 2-1-install-e2e-utils: done
  53. 2-2-rewrite-static-select: done
  54. 2-3-rewrite-async-select: done
  55. 2-4-run-tests-collect-feedback: done
  56. 2-5-fix-found-issues: done
  57. 2-6-stability-validation: done
  58. epic-2-retrospective: done
  59. # Epic 3: 文件上传工具开发与验证
  60. # 目标: 遵循"先验证再扩展"策略,优先开发文件上传工具,解决当前测试超时阻塞问题
  61. # 模式: 工具开发 → 真实 E2E 测试验证 → 问题修复 → 稳定性验证
  62. # 回顾文档: _bmad-output/implementation-artifacts/epic-3-retrospective.md
  63. epic-3: done
  64. 3-1-file-upload-tool: done # 开发文件上传工具函数(含 UI 组件架构改进)
  65. 3-2-upload-unit-tests: done # 编写文件上传工具的单元测试
  66. 3-3-upload-e2e-integration: done # 在 web/tests/e2e 中验证文件上传工具
  67. 3-4-collect-feedback-fix: done # 收集反馈并修复问题(修复了 Select 工具处理带 * 标签的问题)
  68. 3-5-multiple-file-upload: done # 支持多文件同时上传
  69. 3-6-upload-stability-test: done # 文件上传稳定性验证 (6次连续运行 100% 通过)
  70. epic-3-retrospective: done # 回顾完成于 2026-01-11
  71. # Epic 4: 表单工具开发与验证
  72. # 模式: 工具开发 → 真实 E2E 测试验证 → 稳定性验证
  73. epic-4: in-progress
  74. 4-1-form-helper-tool: ready-for-dev # 开发表单辅助工具函数
  75. 4-2-form-unit-tests: backlog # 编写表单工具的单元测试
  76. 4-3-form-e2e-integration: backlog # 在 web/tests/e2e 中验证表单工具
  77. 4-4-form-stability-test: backlog # 表单稳定性验证
  78. epic-4-retrospective: optional
  79. # Epic 5: 列表和对话框工具开发与验证
  80. # 模式: 工具开发 → 真实 E2E 测试验证 → 稳定性验证
  81. epic-5: backlog
  82. 5-1-dynamic-list-dialog-tool: backlog # 开发动态列表和对话框工具函数
  83. 5-2-list-dialog-unit-tests: backlog # 编写列表和对话框的单元测试
  84. 5-3-list-dialog-e2e-integration: backlog # 在 web/tests/e2e 中验证
  85. 5-4-list-dialog-stability-test: backlog # 稳定性验证
  86. epic-5-retrospective: optional
  87. # Epic 6: 完整验证(残疾人管理)
  88. # 状态: backlog - 等待所有工具开发和验证完成
  89. epic-6: backlog
  90. 6-1-complete-flow-test: backlog # 完整流程测试
  91. 6-2-stability-test: backlog # 稳定性测试
  92. epic-6-retrospective: optional
  93. # Epic 7: 完善文档与开发者体验
  94. epic-7: backlog
  95. 7-1-improve-readme-docs: backlog # 完善 README、API 文档和示例
  96. 7-2-vscode-snippets: backlog # VS Code Snippets 和开发体验
  97. epic-7-retrospective: optional
  98. # Epic 8: 区域管理 E2E 测试 (Epic B - 业务测试 Epic)
  99. # 目标: 测试开发者可以为区域管理功能编写完整的 E2E 测试
  100. # 业务分组: Epic B(业务测试 Epic)
  101. # 范围: 省/市/区/街道的添加、编辑、删除和级联选择功能
  102. # 依赖: Epic 9 完成(确保测试隔离和并行执行策略已验证)
  103. epic-8: in-progress
  104. 8-1-region-page-object: done # 创建区域管理 Page Object
  105. 8-2-region-list-test: ready-for-dev # 编写区域列表查看测试
  106. 8-3-add-region-test: backlog # 编写添加区域测试
  107. 8-4-edit-region-test: backlog # 编写编辑区域测试
  108. 8-5-delete-region-test: backlog # 编写删除区域测试
  109. 8-6-cascade-select-test: backlog # 编写级联选择完整流程测试
  110. 8-7-run-tests-collect-issues: backlog # 运行测试并收集问题和改进建议
  111. 8-8-extend-utils-if-needed: backlog # 扩展工具包(如需要)
  112. 8-9-region-stability-test: backlog # 区域管理稳定性验证
  113. epic-8-retrospective: optional
  114. # Epic 9: 残疾人管理完整 E2E 测试覆盖(含并行隔离)
  115. # 目标: 为残疾人管理功能编写完整的、真正验证业务功能的 E2E 测试
  116. # 背景: 现有测试只是组件验证,需要补充完整的业务功能测试
  117. # 模式: 业务测试优先,工具按需扩展(遵循新 PRD 方向)
  118. # 优先级: HIGH - 阻塞 Epic B(区域管理测试)
  119. # 详情参见: _bmad-output/implementation-artifacts/epic-9-plan.md
  120. epic-9: in-progress
  121. 9-1-photo-upload-tests: in-progress # 照片上传功能完整测试(真实上传、多文件、格式验证)
  122. 9-2-bankcard-tests: backlog # 银行卡管理功能测试(添加、编辑、删除)
  123. 9-3-note-tests: backlog # 备注管理功能测试(添加、修改、删除)
  124. 9-4-visit-tests: backlog # 回访记录管理测试(创建、查看、编辑)
  125. 9-5-crud-tests: backlog # 完整流程测试(新增、编辑、删除、查看)
  126. 9-6-parallel-isolation: backlog # 测试隔离与并行执行验证
  127. 9-7-stability-validation: backlog # 稳定性验证(10 次连续运行)
  128. epic-9-retrospective: optional
  129. # Epic 10: 订单管理 E2E 测试 (Epic C - 业务测试 Epic)
  130. # 目标: 测试开发者可以为订单管理功能编写完整的 E2E 测试
  131. # 业务分组: Epic C(业务测试 Epic)
  132. # 范围: 订单 CRUD、状态流转、人员关联、附件管理功能
  133. # 背景: 订单管理是招聘系统的核心业务功能,涉及复杂表单、状态流转、人员关联等场景
  134. # 依赖: Epic 1 和 Epic 2 完成(Select 工具基础)
  135. # 详情参见: _bmad-output/planning-artifacts/epics.md (Epic 10)
  136. epic-10: backlog
  137. 10-1-order-page-object: backlog # 创建订单管理 Page Object
  138. 10-2-order-list-tests: backlog # 编写订单列表查看测试
  139. 10-3-order-filter-tests: backlog # 编写订单搜索和筛选测试
  140. 10-4-order-create-tests: backlog # 编写创建订单测试
  141. 10-5-order-edit-tests: backlog # 编写编辑订单测试
  142. 10-6-order-delete-tests: backlog # 编写删除订单测试
  143. 10-7-order-status-tests: backlog # 编写订单状态流转测试
  144. 10-8-order-detail-tests: backlog # 编写订单详情查看测试
  145. 10-9-order-person-tests: backlog # 编写人员关联功能测试
  146. 10-10-order-attachment-tests: backlog # 编写附件管理测试
  147. 10-11-order-complete-tests: backlog # 编写订单完整流程测试
  148. 10-12-run-tests-collect-issues: backlog # 运行测试并收集问题和改进建议
  149. 10-13-extend-utils-if-needed: backlog # 扩展工具包(如需要)
  150. 10-14-order-stability-test: backlog # 订单管理稳定性验证
  151. epic-10-retrospective: optional
  152. # Epic 组织架构 (2026-01-11):
  153. # =========================
  154. # Epic A: 残疾人管理 E2E 测试 🔄 进行中
  155. # - Epic 1: 测试工具包基础框架与 Select 支持 ✅
  156. # - Epic 2: 在现有 E2E 测试中验证 Select 工具 ✅
  157. # - Epic 3: 文件上传工具开发与验证 ✅
  158. # - Epic 9: 残疾人管理完整 E2E 测试覆盖(含并行隔离)🆕 当前优先级
  159. #
  160. # Epic B: 区域管理 E2E 测试 ⏸️ 等待 Epic 9 完成
  161. # - Epic 8: 区域管理 E2E 测试
  162. #
  163. # Epic C: 订单管理 E2E 测试 📋 待开发
  164. # - Epic 10: 订单管理 E2E 测试 (核心业务功能)
  165. #
  166. # Epic D: e2e-test-utils 包维护 🌟 支持性任务
  167. # - Epic 4: 表单工具开发与验证
  168. # - Epic 5: 列表和对话框工具开发与验证
  169. # - Epic 6: 完整验证(已合并到 Epic 9)
  170. # - Epic 7: 文档与开发者体验
  171. #
  172. # 新 PRD 方向(2026-01-11 修订):
  173. # - 业务测试优先(主目标)
  174. # - 工具自然演进(副目标)
  175. # - Epic 优先级建议:Epic B(简单)→ Epic C(复杂核心业务)
  176. # 技术改进完成状态 (2026-01-10):
  177. # ================================
  178. # - HIGH: 配置 ESLint 规则捕获常见问题 ✅
  179. # - HIGH: 更新架构文档记录 TypeScript + Playwright 陷阱 ✅
  180. # - HIGH: 创建开发者自查清单 ✅
  181. # 详情参见:
  182. # - packages/e2e-test-utils/eslint.config.js
  183. # - _bmad-output/planning-artifacts/architecture.md (新增 TypeScript+Playwright 陷阱部分)
  184. # - packages/e2e-test-utils/docs/DEVELOPER_CHECKLIST.md