41 lines
2.6 KiB
Markdown
41 lines
2.6 KiB
Markdown
|
|
# 结果总览员工结果表前端验证记录
|
|||
|
|
|
|||
|
|
## 验证范围
|
|||
|
|
|
|||
|
|
- 结果总览既有接口路径保持不变
|
|||
|
|
- 模型区人员查询参数透传保持不变
|
|||
|
|
- 结果总览入口页并发取数结构保持不变
|
|||
|
|
- 风险仪表盘、风险人员总览、模型区与风险明细区展示边界保持不变
|
|||
|
|
- 页面不重新引入已移除的 TOP10 区块
|
|||
|
|
|
|||
|
|
## 执行日期
|
|||
|
|
|
|||
|
|
- 2026-03-22
|
|||
|
|
|
|||
|
|
## 验证命令
|
|||
|
|
|
|||
|
|
```bash
|
|||
|
|
cd ruoyi-ui
|
|||
|
|
node tests/unit/project-overview-api.test.js
|
|||
|
|
node tests/unit/preliminary-check-api-integration.test.js
|
|||
|
|
node tests/unit/preliminary-check-summary-and-people.test.js
|
|||
|
|
node tests/unit/preliminary-check-model-and-detail.test.js
|
|||
|
|
node tests/unit/preliminary-check-risk-people-binding.test.js
|
|||
|
|
node tests/unit/preliminary-check-model-linkage-flow.test.js
|
|||
|
|
```
|
|||
|
|
|
|||
|
|
## 每条命令结果
|
|||
|
|
|
|||
|
|
- `node tests/unit/project-overview-api.test.js`:`exit 0`,确认 `/ccdi/project/overview/dashboard`、`/ccdi/project/overview/risk-people`、`/ccdi/project/overview/risk-models/cards`、`/ccdi/project/overview/risk-models/people` 4 个接口路径仍为当前前端契约,模型区人员分页参数继续按既有字段透传。
|
|||
|
|
- `node tests/unit/preliminary-check-api-integration.test.js`:`exit 0`,确认入口页仍通过 `Promise.all` 并发请求仪表盘、风险人员总览、模型卡片 3 类接口,未感知结果表底层实现。
|
|||
|
|
- `node tests/unit/preliminary-check-summary-and-people.test.js`:`exit 0`,确认风险仪表盘继续展示 `总人数`、`高风险`、`中风险`、`低风险`、`无风险人员`,风险人员总览继续展示姓名、身份证号、所属部门、风险等级、命中模型数、核心异常点。
|
|||
|
|
- `node tests/unit/preliminary-check-model-and-detail.test.js`:`exit 0`,确认模型区仍保留 `ANY / ALL`、关键词筛选、部门筛选与异常标签展示,风险明细区静态结构未被破坏。
|
|||
|
|
- `node tests/unit/preliminary-check-risk-people-binding.test.js`:`exit 0`,确认风险人员总览仍绑定 `overviewList`,核心异常点支持标签归一化,且未回退到 `topRiskList`。
|
|||
|
|
- `node tests/unit/preliminary-check-model-linkage-flow.test.js`:`exit 0`,确认模型卡片选中/取消、重置、分页与参数构造仍按既有联动流程工作。
|
|||
|
|
|
|||
|
|
## 结论
|
|||
|
|
|
|||
|
|
- 结果总览页前端未新增页面和交互,当前实现已满足“后端改为员工结果表出数后前端契约不变”的要求。
|
|||
|
|
- 本轮主要收益是把现有稳定行为沉淀为显式单测,降低后续改动引入接口漂移、展示漂移或联动回归的风险。
|
|||
|
|
- 本轮验证仅执行前端 Node 单测脚本,未启动额外前后端进程,因此无需执行进程清理。
|