Back to Details

run-smoke-tests

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Run smoke tests

运行冒烟测试

Trigger

触发条件

Need end-to-end smoke verification before or after changes.
在变更前后需要进行端到端冒烟验证。

Workflow

工作流程

  1. Build prerequisites for the target app.
  2. Run the relevant smoke suite or a focused test file.
  3. If failing, inspect traces/logs and isolate the root cause.
  4. Apply a minimal fix and rerun until stable.
  1. 构建目标应用的前置依赖。
  2. 运行相关的冒烟测试套件或指定的测试文件。
  3. 若测试失败，检查追踪信息/日志并定位根本原因。
  4. 应用最小化修复并重新运行，直到测试稳定通过。

Example Commands

示例命令

bash
undefined
bash
undefined

Run full smoke suite

运行完整的冒烟测试套件

npm run smoketest
npm run smoketest

Run a specific smoke test file

运行指定的冒烟测试文件

npm run smoketest -- path/to/test.spec.ts
npm run smoketest -- path/to/test.spec.ts

Faster iteration when build artifacts are ready

当构建产物已就绪时，更快迭代

npm run smoketest-no-compile -- path/to/test.spec.ts
undefined
npm run smoketest-no-compile -- path/to/test.spec.ts
undefined

Guardrails

防护措施

  • Prefer deterministic waits and assertions over brittle timeouts.
  • Re-run passing fixes to reduce flaky false positives.
  • Quarantine tests only when explicitly requested and documented.
  • 优先使用确定性等待和断言，而非不可靠的超时设置。
  • 重新运行已通过的修复，减少不稳定的误报。
  • 仅在明确要求并记录的情况下隔离测试。

Output

输出内容

  • Test results summary
  • Root cause and fix
  • Remaining flake risk (if any)
  • 测试结果汇总
  • 根本原因与修复方案
  • 剩余的不稳定风险（如有）