Back to Details

w-debug-browser

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
Use the affected URL, expected interaction, and available browser tools. Inspect the app's README and browser-testing conventions first.
  1. Reproduce the interaction and collect relevant DOM, network, and console evidence before adding instrumentation.
  2. Trace the failure to its owning client or server boundary. Use the repository logger for necessary temporary traces; avoid secrets in captured output.
  3. Apply the smallest authorized fix, then replay the same interaction and relevant failure or empty states.
  4. Run affected automated checks and remove temporary traces introduced here. Distinguish runtime evidence from automated results. If tools or credentials block reproduction, report the exact limitation rather than looping without new evidence.
  5. Docs: 
    /w-docs
    if behavior or commands changed.
使用受影响的 URL、预期交互以及可用的浏览器工具。先检查应用的 README 和浏览器测试约定。
  1. 在添加 instrumentation 之前，复现该交互并收集相关的 DOM、network 和 console 证据。
  2. 将故障追踪到负责它的客户端或服务端边界。必要时使用仓库 logger 添加临时追踪；避免在捕获的输出中包含 secrets。
  3. 应用授权范围内的最小修复，然后重放相同的交互以及相关的失败或空状态。
  4. 运行受影响的自动化检查，并移除此处引入的临时追踪。区分运行时证据与自动化结果。如果工具或凭据阻碍复现，应报告确切限制，而不是在没有新证据的情况下反复尝试。
  5. 文档：如果行为或命令发生变化，更新 
    /w-docs
    。