fix(e2e): 更新生成流程E2E测试适配7步新流程 #663

Merged
auto-approve-bot merged 1 commits from fix/e2e-generation-7step-flow into develop 2026-07-21 00:37:49 +08:00
Owner

问题

前端生成页已从 5 步流程升级为 7 步流程(新增「生成预览」和「选择封面」两个步骤),但 E2E 测试 core-generation.spec.ts 仍使用旧的 5 步断言,导致 Staging E2E Tests 持续失败。

失败用例:walks through 5-step wizard and starts generation
报错:Step 3 预期「选择标题」heading,实际页面显示「生成预览」

修复

  • 更新测试步骤断言从 5 步适配到 7 步
  • Step 3:生成预览 — 纯展示页,直接点下一步
  • Step 6:选择封面 — 默认 AI 智能选帧模式,无必填项,直接点下一步
  • 原标题/配音/确认生成步骤序号相应后移

验证

Staging E2E Tests 通过即可验证修复有效。

## 问题 前端生成页已从 5 步流程升级为 7 步流程(新增「生成预览」和「选择封面」两个步骤),但 E2E 测试 `core-generation.spec.ts` 仍使用旧的 5 步断言,导致 Staging E2E Tests 持续失败。 失败用例:`walks through 5-step wizard and starts generation` 报错:Step 3 预期「选择标题」heading,实际页面显示「生成预览」 ## 修复 - 更新测试步骤断言从 5 步适配到 7 步 - **Step 3:生成预览** — 纯展示页,直接点下一步 - **Step 6:选择封面** — 默认 AI 智能选帧模式,无必填项,直接点下一步 - 原标题/配音/确认生成步骤序号相应后移 ## 验证 Staging E2E Tests 通过即可验证修复有效。
xiaoxia added 1 commit 2026-07-21 00:35:11 +08:00
fix(e2e): 更新 core-generation 测试适配 7 步生成流程
CI/CD Pipeline / Build Staging API Image (pull_request) Has been skipped
CI/CD Pipeline / Build Staging Web Image (pull_request) Has been skipped
CI/CD Pipeline / Build Staging Worker Image (pull_request) Has been skipped
CI/CD Pipeline / Deploy Staging (Watchtower auto-deploy) (pull_request) Has been skipped
CI/CD Pipeline / Build Production API Image (pull_request) Has been skipped
CI/CD Pipeline / Build Production Web Image (pull_request) Has been skipped
CI/CD Pipeline / Staging E2E Tests (pull_request) Has been skipped
CI/CD Pipeline / Staging API Integration Tests (pull_request) Has been skipped
CI/CD Pipeline / Build Production Worker Image (pull_request) Has been skipped
CI/CD Pipeline / ACR Image Cleanup (pull_request) Has been skipped
CI/CD Pipeline / Deploy Production (pull_request) Has been skipped
CI/CD Pipeline / Production Browser E2E (pull_request) Has been skipped
CI/CD Pipeline / Check if frontend-only change (pull_request) Successful in 13s
CI/CD Pipeline / Validate Code Quality And Tests (pull_request) Has been skipped
CI/CD Pipeline / Unit Tests (pull_request) Has been skipped
CI/CD Pipeline / Integration Tests (pull_request) Has been skipped
Preview Deploy / Deploy Preview Environment (pull_request) Successful in 1m16s
CI/CD Pipeline / Frontend Lint (pull_request) Successful in 1m25s
PR Automation / Auto Approve on CI Green (pull_request) Successful in 1m27s
AI Code Review / AI Code Review (pull_request) Successful in 1m38s
CI/CD Pipeline / Frontend Unit Tests (pull_request) Successful in 2m16s
PR Automation / Auto Merge on CI Green + Approved (pull_request) Successful in 2m37s
Preview Cleanup / Cleanup Preview Environment (pull_request) Successful in 19s
9286466d5d
前端生成页从 5 步改为 7 步(新增生成预览 + 选择封面),
E2E 测试用例已过期导致 Staging E2E 失败。

变更:
- Step 3: 新增「生成预览」步骤(纯展示,直接下一步)
- Step 6: 新增「选择封面」步骤(默认 AI 智能模式,直接下一步)
- 原步骤序号相应后移

🚀 预览环境已部署

项目 详情
PR号 #663
预览链接 https://pr-663.preview.xiaoxiajianji.com
API环境 staging

💡 预览环境使用 staging API 数据,请勿在预览环境中操作重要数据。

🔄 每次提交新代码后预览环境会自动更新。

🗑️ PR 关闭或合并后,预览环境会自动清理。

🚀 **预览环境已部署** | 项目 | 详情 | |------|------| | PR号 | #663 | | 预览链接 | [https://pr-663.preview.xiaoxiajianji.com](https://pr-663.preview.xiaoxiajianji.com) | | API环境 | staging | > 💡 预览环境使用 staging API 数据,请勿在预览环境中操作重要数据。 > > 🔄 每次提交新代码后预览环境会自动更新。 > > 🗑️ PR 关闭或合并后,预览环境会自动清理。
auto-approve-bot approved these changes 2026-07-21 00:36:39 +08:00
auto-approve-bot left a comment
Collaborator

CI全绿,自动审批通过。

CI全绿,自动审批通过。
auto-approve-bot approved these changes 2026-07-21 00:36:39 +08:00
auto-approve-bot left a comment
Collaborator

CI全绿,自动审批通过。

CI全绿,自动审批通过。
Collaborator

📊 审查概览

  • 整体评价:通过
  • 严重问题数量:0 个
  • 一般建议数量:0 个

需修改的问题(严重)

💡 改进建议(一般)

良好实践

  1. 使用推荐的选择器策略:代码中使用了 page.getByRole("heading", ...)page.getByRole("button", ...),这是 Playwright 推荐的最佳实践,能够提高测试的稳定性和可访问性。
  2. 清晰的注释维护:在增加新步骤时,同步更新了注释中的步骤编号(Step 3 到 Step 7),保证了代码注释与实际逻辑的一致性,便于后续维护。
  3. 逻辑结构清晰:E2E 测试流程按照用户操作步骤线性编写,等待断言(toBeVisible)与操作(click)搭配合理,符合自动化测试编写规范。

🤖 由 AI 代码审查机器人自动生成 | 2026-07-21 00:36:49 | 模型:

### 📊 审查概览 - 整体评价:通过 - 严重问题数量:0 个 - 一般建议数量:0 个 ### ❌ 需修改的问题(严重) 无 ### 💡 改进建议(一般) 无 ### ✅ 良好实践 1. **使用推荐的选择器策略**:代码中使用了 `page.getByRole("heading", ...)` 和 `page.getByRole("button", ...)`,这是 Playwright 推荐的最佳实践,能够提高测试的稳定性和可访问性。 2. **清晰的注释维护**:在增加新步骤时,同步更新了注释中的步骤编号(Step 3 到 Step 7),保证了代码注释与实际逻辑的一致性,便于后续维护。 3. **逻辑结构清晰**:E2E 测试流程按照用户操作步骤线性编写,等待断言(`toBeVisible`)与操作(`click`)搭配合理,符合自动化测试编写规范。 --- <sub>🤖 由 AI 代码审查机器人自动生成 | 2026-07-21 00:36:49 | 模型: </sub> <!-- AI_CODE_REVIEW_AUTO_COMMENT -->
auto-approve-bot merged commit 3a8da7ea12 into develop 2026-07-21 00:37:49 +08:00
auto-approve-bot deleted branch fix/e2e-generation-7step-flow 2026-07-21 00:37:49 +08:00

🗑️ 预览环境已清理

PR #663 已关闭或合并,对应的预览环境已被清理。

如有需要,可以重新打开 PR 来重新生成预览环境。

🗑️ **预览环境已清理** PR #663 已关闭或合并,对应的预览环境已被清理。 > 如有需要,可以重新打开 PR 来重新生成预览环境。
Sign in to join this conversation.