@luolingp/request-doctor 0.16.3 → 0.16.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/docs/01-/350/275/257/344/273/266/351/234/200/346/261/202/350/247/204/346/240/274/350/257/264/346/230/216.md +1 -1
- package/docs/02-/350/275/257/344/273/266/350/256/276/350/256/241/350/257/264/346/230/216.md +1 -1
- package/docs/03-/350/275/257/344/273/266/346/265/213/350/257/225/346/212/245/345/221/212.md +4 -3
- package/docs/04-/345/256/211/350/243/205/351/203/250/347/275/262/350/257/264/346/230/216.md +1 -1
- package/docs/05-/347/224/250/346/210/267/346/211/213/345/206/214.md +1 -1
- package/docs/06-/350/275/257/344/273/266/350/264/250/351/207/217/345/272/246/351/207/217/346/212/245/345/221/212.md +1 -1
- package/docs/quality-report.json +1 -1
- package/package.json +1 -1
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
# 软件测试报告
|
|
2
2
|
|
|
3
3
|
**产品名称**：request-doctor（请求急救员）
|
|
4
|
-
**版本**：0.16.
|
|
4
|
+
**版本**：0.16.4
|
|
5
5
|
**编制依据**：GB/T 8567-2006《计算机软件文档编制规范》6.6；GB/T 8566-2007 验证与确认过程
|
|
6
6
|
|
|
7
7
|
---
|
|
@@ -62,6 +62,7 @@
|
|
|
62
62
|
| `test/client-half.test.mjs` | 11 | 客户端半：模块身份、注入声明、apply 注册、组件能渲染 |
|
|
63
63
|
| `test/diagnostics.test.mjs` | 3 | 快照可选写入：不配置不写盘、突发合并、坏路径不致命 |
|
|
64
64
|
| `test/restart-notice.test.mjs` | 3 |
|
|
65
|
+
| `test/write-timing.test.mjs` | 3 | 写盘时序：合并窗口内手动写仍是最新、多次记录只排一个写 |
|
|
65
66
|
| `test/restart-cycle.test.mjs` | 3 | 真跨重启：写盘后新建诊断读同一文件，记录与次数都在 |
|
|
66
67
|
| `test/status-restore.test.mjs` | 7 | 跨重启恢复：快照可读、缺失/损坏/旧格式均当无历史、非法条目丢弃 |
|
|
67
68
|
| `test/status-path.test.mjs` | 6 | 诊断落盘路径：默认兜底、空串表示不写、非字符串当未设 |
|
|
@@ -77,7 +78,7 @@
|
|
|
77
78
|
| `test/panel-blocked.test.mjs` | 7 | 冲突判定：审计兼容却被拒装、清单形状解析、给 allow 动作 |
|
|
78
79
|
| `test/panel-briefs.test.mjs` | 6 | 界面摘要：按名索引、只送可见行、缺数据不抛、不污染诊断 |
|
|
79
80
|
| `test/verdict-report.test.mjs` | 29 | why 与 list：判定、理由、环境摘要、自动扫描、分组、缺口、按形态给建议 | 缺导出判为需要重启；其它失败不误判；多次累积不覆盖 |
|
|
80
|
-
| **合计** | **
|
|
81
|
+
| **合计** | **265** | **全部通过** |
|
|
81
82
|
|
|
82
83
|
执行结果：
|
|
83
84
|
|
|
@@ -231,7 +232,7 @@
|
|
|
231
232
|
|
|
232
233
|
### 7.2 分文件执行结果
|
|
233
234
|
|
|
234
|
-
|
|
235
|
+
45 个测试文件逐个单独执行，每个都有用例且全部通过，不存在因导入失败而静默跳过的文件。用例数分布：compat.test.mjs 17、plugin.test.mjs 15、compat-env.test.mjs 14、classify.test.mjs 13，其余按职能分散，合计 265。
|
|
235
236
|
## 8 覆盖率实测
|
|
236
237
|
|
|
237
238
|
用 Node 自带的 `--experimental-test-coverage` 跑一遍，作为「分支有没有被真的走一遍」的证据。这不替代对断言质量的判断，只说明哪些代码从未被执行。
|
package/docs/quality-report.json
CHANGED