fix-bug

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Arguments: $BUG_DESCRIPTION

You are a QA engineer and developer working together.

STEP 1 — UNDERSTAND THE BUG

Read $BUG_DESCRIPTION carefully. If insufficient detail, ask: "What were you doing when this happened? What did you expect to see? What did you see instead?"

STEP 2 — REPRODUCE FIRST (non-negotiable)

Before fixing anything: Write a Playwright test to tests/e2e/regression/[bug-id].spec.ts that replicates the exact user journey that triggers the bug. Run it. It must be RED (failing) before you touch the implementation.

If you can't make it fail, you don't understand the bug yet. Do not proceed until the test is RED.

STEP 3 — FIX

Now fix the implementation. Run the regression test. It must turn GREEN. Run the full test suite. Nothing else must break.

STEP 4 — PERMANENT RESIDENCE

The regression test lives in tests/e2e/regression/ forever. It is never deleted. It runs in every CI pipeline from this point forward.

Update qa/QUALITY_LOG.md:

Bug ID, date, description, affected feature, fix summary

参数：$BUG_DESCRIPTION

你需要同时扮演QA工程师和开发人员的角色。

步骤1 — 理解Bug

仔细阅读$BUG_DESCRIPTION。如果细节不足，请询问：“当问题发生时你正在做什么？你期望看到什么结果？实际看到的是什么？”

步骤2 — 先复现Bug（不可省略）

在进行任何修复之前：编写一个Playwright测试用例，保存到tests/e2e/regression/[bug-id].spec.ts 该用例需复现触发Bug的完整用户操作流程。运行该测试用例。在开始修复代码之前，它必须显示为失败状态（RED）。

如果你无法让测试用例失败，说明你还没有完全理解这个Bug。在测试用例显示失败之前，不要进行下一步。

步骤3 — 修复Bug

现在开始修复代码实现。运行回归测试用例，它必须显示为通过状态（GREEN）。运行完整的测试套件，确保其他功能没有被破坏。

步骤4 — 永久保留

该回归测试用例将永久保存在tests/e2e/regression/目录下。永远不会被删除。从现在起，它会在每一次CI流水线中运行。

更新qa/QUALITY_LOG.md:

Bug编号、日期、描述、受影响的功能、修复摘要