规划OA产品流程测试与制度对齐任务(05-27-oa-product-flow-test-policy-audit)
这个提交包含在:
@@ -0,0 +1,3 @@
|
||||
{"file": ".trellis/spec/hyb-oa/docs-and-evidence.md", "reason": "Validate test matrix and generated reports follow evidence contracts"}
|
||||
{"file": ".trellis/spec/hyb-oa/deployment-trialrun.md", "reason": "Validate public smoke and live-readiness claims"}
|
||||
{"file": ".trellis/spec/hyb-oa/security-privacy.md", "reason": "Validate automated test evidence is redacted"}
|
||||
@@ -0,0 +1,5 @@
|
||||
{"file": ".trellis/spec/hyb-oa/project-governance.md", "reason": "Trellis task and phased implementation boundaries"}
|
||||
{"file": ".trellis/spec/hyb-oa/docs-and-evidence.md", "reason": "Test evidence, reportRef and finding aggregation contracts"}
|
||||
{"file": ".trellis/spec/hyb-oa/deployment-trialrun.md", "reason": "Public OA smoke, live readiness and deployment verification boundaries"}
|
||||
{"file": ".trellis/spec/hyb-oa/security-privacy.md", "reason": "Test reports must not persist secrets or sensitive business data"}
|
||||
{"file": ".trellis/spec/hyb-oa/frontend-react-vite-design.md", "reason": "Frontend visual and interaction test expectations"}
|
||||
@@ -0,0 +1,18 @@
|
||||
# 实施策略
|
||||
|
||||
## Planning 口径
|
||||
|
||||
本子任务先保持 planning。总任务完成后,再启动测试覆盖专项。
|
||||
|
||||
## 后续执行方式
|
||||
|
||||
1. 列出规划业务流程和关键异常场景。
|
||||
2. 逐项盘点后端、PC、移动、企业微信 UA/真机和公网只读巡检覆盖。
|
||||
3. 标记缺口等级:阻断、重要、体验、低频管理。
|
||||
4. 分批补齐测试,优先权限、状态机、核心提交/审批/付款闭环。
|
||||
|
||||
## 边界
|
||||
|
||||
- 不自动创建真实业务数据。
|
||||
- 不执行真实付款、ERP 写入、企业微信写入或数据库重置。
|
||||
- 不把只读巡检误写成完整业务写入测试通过。
|
||||
@@ -0,0 +1,48 @@
|
||||
# 业务流程自动化测试覆盖矩阵与补齐
|
||||
|
||||
## Goal
|
||||
|
||||
盘点 OA 规划业务流程是否已经被后端和前端自动化测试覆盖,形成“业务流程 -> 后端测试 -> PC E2E -> 移动 E2E -> 企业微信 UA/真机 -> 公网只读巡检”的覆盖矩阵,并分批补齐缺口。
|
||||
|
||||
## Scope
|
||||
|
||||
- 报销/PDF OCR/查重/审批/驳回/撤回/归档。
|
||||
- 审批中心、通知、企业微信 deeplink、权限和自审阻断。
|
||||
- 财务付款批次、线下付款、银行回单、已付款、AP 导出。
|
||||
- 采购/费用、合同台账、项目、资产、系统管理、审计日志。
|
||||
- 后端 API/服务/权限/状态机测试和前端 PC/移动/企业微信 E2E 均纳入。
|
||||
|
||||
## Requirements
|
||||
|
||||
- 建立业务流程清单和自动化测试覆盖矩阵。
|
||||
- 标记已覆盖、部分覆盖、仅只读覆盖、缺测试、需要人工真机验证的流程。
|
||||
- 区分阻断级测试缺口和体验型测试缺口。
|
||||
- 给出补齐顺序,先补核心业务闭环和权限/状态机,再补页面视觉和低频管理页。
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] 输出测试覆盖矩阵。
|
||||
- [ ] 明确每条业务流程是否有后端和前端覆盖。
|
||||
- [ ] 明确公网试运行只读巡检不能替代真实业务写入流程测试。
|
||||
- [ ] 给出第一批要补的测试清单和命令。
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- 本 planning 任务不直接新增测试代码。
|
||||
- 不自动创建真实业务数据。
|
||||
- 不执行真实付款、ERP 写入、企业微信写入或数据库重置。
|
||||
|
||||
## Test Plan
|
||||
|
||||
```bash
|
||||
python3 ./.trellis/scripts/task.py validate 05-27-oa-test-coverage-matrix
|
||||
node scripts/qa/check-trellis-governance.mjs
|
||||
git diff --check
|
||||
```
|
||||
|
||||
## Technical Notes
|
||||
|
||||
- Trial runbook: `docs/试运行与自动化验证手册.md`
|
||||
- Testing facts: `docs/测试规约与回归门禁.md`
|
||||
- Daily runner: `scripts/qa/run-oa-real-use-daily.sh`
|
||||
- Final readiness runner: `scripts/qa/run-oa-final-launch-readiness.sh`
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"id": "oa-test-coverage-matrix",
|
||||
"name": "oa-test-coverage-matrix",
|
||||
"title": "业务流程自动化测试覆盖矩阵与补齐",
|
||||
"description": "盘点并补齐OA规划业务流程的后端、前端PC、移动和企业微信自动化测试覆盖。",
|
||||
"status": "planning",
|
||||
"dev_type": null,
|
||||
"scope": "qa-coverage-governance",
|
||||
"package": null,
|
||||
"priority": "P1",
|
||||
"creator": "shunli",
|
||||
"assignee": "shunli",
|
||||
"createdAt": "2026-05-27",
|
||||
"completedAt": null,
|
||||
"branch": null,
|
||||
"base_branch": "main",
|
||||
"worktree_path": null,
|
||||
"commit": null,
|
||||
"pr_url": null,
|
||||
"subtasks": [],
|
||||
"children": [],
|
||||
"parent": "05-27-oa-product-flow-test-policy-audit",
|
||||
"relatedFiles": [],
|
||||
"notes": "",
|
||||
"meta": {}
|
||||
}
|
||||
在新工单中引用
屏蔽一个用户