Back to Details

resolve-qa-feedback

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
  1. Reproduce the tester’s exact report with 
    /diagnosing-bugs
    . Use the reported environment, steps, and observable behavior. Record a human-readable red baseline. If it does not reproduce, stop and report the exact blocker.
  2. Fix the reproduced problem with 
    /develop
    . Use TDD where the behavior has a stable test seam.
  3. Repeat the tester’s exact steps on the fixed pull-request build. Confirm the reported failure is absent and the expected behavior occurs.
  4. Capture human-readable evidence, such as screenshots or a continuous video. The evidence must show:
    • the relevant initial state;
    • the tester’s actions;
    • the application’s response;
    • the expected final state.
  5. Inspect the evidence before reporting success. If it is unclear, incomplete, or shows incorrect behavior, continue fixing or recapture it. Finish only when the evidence visibly proves the exact QA report is resolved.
  1. 使用
    /diagnosing-bugs
    精准复现测试人员的报告内容。使用报告中提及的环境、步骤和可观察行为。记录一份易读的错误基准。如果无法复现，请停止操作并报告具体的阻碍因素。
  2. 使用
    /develop
    修复已复现的问题。若该行为存在稳定的测试切入点，采用TDD（测试驱动开发）方式。
  3. 在修复后的拉取请求构建版本上重复测试人员的精准步骤。确认报告中的问题已消失，且符合预期行为。
  4. 收集易读的证据，例如截图或连续录制的视频。证据必须包含：
    • 相关的初始状态；
    • 测试人员的操作步骤；
    • 应用程序的响应；
    • 预期的最终状态。
  5. 在报告问题解决前核查证据。如果证据不清晰、不完整或显示行为异常，请继续修复或重新收集证据。只有当证据能够直观证明该QA报告中的问题已完全解决时，方可结束流程。