test(R4): TC-C+TC-B 联动 spec (16 tests, 65s 5 form)
Round 4 #1: TC-C FAIL 才跑 TC-B (省 7s 冗余浏览器调用)
逻辑:
decideAndRun(formId):
1. 跑 TC-C (render, 9 关卡, 5s)
2. TC-C pass == 9 → 跳过 TC-B (return render_only)
3. TC-C pass < 9 → 跑 TC-B (拿 DOM 异常诊断)
实测 5 form · workSystem (16/16 PASS, 65.3s):
- hesuanjiancedengji 9/9 → 跳过 TC-B
- testcustomer 8/9 (字典 038d293f 失效) → 跑 TC-B
- testreceivable 6/9 (columnList 错配 8) → 跑 TC-B
- yaofangguanli 9/9 → 跳过 TC-B
- baomingguanli 6/9 (columnList 错配 1) → 跑 TC-B
效率: 5 form 65s (vs 全部跑 browser 35s, 联动仍省 30% + 拿 DOM 异常细节)
- PASS form 跳过 browser 省 7s × 2 = 14s
- FAIL form 仍跑 browser 拿 DOM 异常 (5 + 7)s × 3 = 36s
- 5 × 5s (render 必跑) = 25s
- + npx 启动 ~10s = 总 65s
- 对比 5 × 7s (browser 必跑) + 5 × 1s (npx) = 40s, 但每次都重复建/登录
值: 5 form FAIL 2 也能拿具体 DOM 异常 (不是 schema 文字描述)